Actions
Bug #23610
closedpg stuck in activating because of dropped pg-temp message
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
1. mon sent pg-create(1.0) to osd.1
2. osd.1 created 1.0 with acting set of [1,0]. pg 1.0 was active+clean by then.
3. osd.0 was down
4. osd.1 consumed the new osdmap, the up and acting set of pg 1.0 were [1,2], it started peering.
5. osd.1 notified osd.2 that it should create replica of pg 1.0
6. osd.2 withheld the creating of pg 1.0 because its "max-pg-per-osd" was 1
7. osd.2 removed all created pgs
8. osd.2 tried to a osd-pgtemp to mon. but the connection was reset.
9. osd.2 reconnected to mon, but the osd-pgtemp was not resent because the osd-mon connection is lossy.
10.osd.2 never resent the osd-pgtemp..
Updated by Kefu Chai about 6 years ago
- Status changed from New to Fix Under Review
Updated by Nathan Cutler about 6 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 6 years ago
- Copied to Backport #23630: luminous: pg stuck in activating added
Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Fix Under Review
Updated by Kefu Chai about 6 years ago
- Related to Bug #23648: max-pg-per-osd.from-primary fails because of activating pg added
Updated by Kefu Chai about 6 years ago
- Subject changed from pg stuck in activating to pg stuck in activating because of dropped pg-temp message
Updated by Kefu Chai about 6 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved
Actions