Project

General

Profile

Actions

Documentation #17871

closed

crush-map document could use clearer warning about impact of changing tunables

Added by Jason Jensen over 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

In http://docs.ceph.com/docs/jewel/rados/operations/crush-map/ this section is the closest thing to documenting the impact on connected clients after updating the tunables.

"The ceph-osd and ceph-mon daemons will start requiring the feature bits of new connections as soon as they get the updated map. However, already-connected clients are effectively grandfathered in, and will misbehave if they do not support the new feature."

This section could be clarified to warn that clients will stop functioning completely. This section is also buried far down the document and not in an obvious location in the document to warn of the impact of modifying tunables. Sections earlier in the document talk about data migration and performance impacts. Perhaps the warning about client connectivity should be included near these sections on impacts.

Actions #1

Updated by Loïc Dachary over 7 years ago

  • Category changed from documentation to 10
Actions #2

Updated by Greg Farnum almost 7 years ago

  • Project changed from Ceph to RADOS
  • Category deleted (10)
Actions #3

Updated by Zac Dover over 4 years ago

  • Assignee set to Zac Dover
Actions #4

Updated by Zac Dover over 3 years ago

  • Status changed from New to Closed

Josh and I spoke about this and agreed that this doesn't require an explicit warning.
I am changing the status of this bug to CLOSED.

Actions

Also available in: Atom PDF