mgr: process map before notifying clients#56047
Conversation
Oddly the maps are processed after notifying the modules. I'm not sure if this actually can cause modules to read from the old maps (since finisher contexts are queued) but it seemed odd. Fixes: https://tracker.ceph.com/issues/64799 Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
* refs/pull/56047/head: mgr: process map before notifying clients
* refs/pull/56047/head: mgr: process map before notifying clients
* refs/pull/56047/head: mgr: process map before notifying clients
* refs/pull/56047/head: mgr: process map before notifying clients
|
https://tracker.ceph.com/issues/65215#note-8 Good to merge. |
|
Hmm are you sure there's not some weird reason for this? I could definitely see one of the modules needing to do something before the mgr process triggers everything else, though it would be gross. Did you do some git archaeology to see where it came from? |
The call to ac30e6c#diff-cf12a9b0314445319a3f842090e100e08a1181f469acc37c09ee4387ce4005b6R488-R491 In any case, the reversed update was also present for |
|
This PR is under test in https://tracker.ceph.com/issues/65530. |
rzarzynski
left a comment
There was a problem hiding this comment.
LGTM. However, let's not hurry up with backporting this chnage. IMHO it deserves some baking in main.
| case CEPH_MSG_MON_MAP: | ||
| /* MonClient passthrough of MonMap to us */ | ||
| handle_mon_map(); /* use monc's monmap */ | ||
| py_module_registry->notify_all("mon_map", ""); |
There was a problem hiding this comment.
Now this looks far more intuitive / less weird.
The call to
handle_fs_maphas always been that way. John actually mentioned a race possibility in the comment in that method:
OK, so this peculiar order has not been brought by any fix commit.
|
This PR is under test in https://tracker.ceph.com/issues/65562. |
|
This PR is under test in https://tracker.ceph.com/issues/65596. |
Oddly the maps are processed after notifying the modules. I'm not sure if this actually can cause modules to read from the old maps (since finisher contexts are queued) but it seemed odd.
Fixes: https://tracker.ceph.com/issues/64799
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e