Actions
Bug #11197
closedpg stuck stale after create with activation delay
% Done:
0%
Source:
Q/A
Tags:
Backport:
firefly
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
I think as soon as the mon gets a status from an osd(peering for instance), the pg moves off of the creating list and we stop sending creates. However, if the primary dies between sending that status and the replicas recording the initial activation, it will not have been written out on any other osd and will end up without any copies, yet not creating. As a bandaid, we can choose not to move it out of creating state until we activate?
(Not a hammer blocker, very very old bug as far as I can tell)
Actions