Bug #46914
closed
Looking through the source, there's one clear way this happens: the leader may decide that a message can get dropped in preprocess_pgtemp() where the peon disagreed. That will usually involve some kind of race in changing states (eg, OSD getting marked down), but it seems possible.
So, just mark the op as no_reply when dropping the message.
- Status changed from New to Fix Under Review
- Backport set to octopus, nautilus
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #47091: octopus: mon: stuck osd_pgtemp message forwards added
- Copied to Backport #47092: nautilus: mon: stuck osd_pgtemp message forwards added
- Pull request ID set to 36593
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF