Bug #11197
closedpg stuck stale after create with activation delay
0%
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)
Updated by Samuel Just about 9 years ago
- Status changed from New to 7
I'm somewhat wrong, the problem is that we don't set creating at all when handling the initial create message. It gets set on the first start_peering_interval after that point.
Updated by Sage Weil about 9 years ago
- Status changed from 7 to Pending Backport
- Source changed from other to Q/A
- Backport set to firefly
Updated by Xinxin Shu about 9 years ago
- firefly backport https://github.com/ceph/ceph/pull/4384
Updated by Loïc Dachary almost 9 years ago
29bc9e5 PG: set/clear CREATING in Primary state entry/exit (in firefly),
Updated by Loïc Dachary almost 9 years ago
- Status changed from Pending Backport to Resolved