Actions
Bug #15709
closedExclusive lock not properly released if journal non-primary
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If exclusive lock fails to be acquired because the journal is non-primary (replay cannot proceed), the lock is not released on disk. This can cause the rbd-mirror daemon to accidentally blacklist itself if it retries acquiring the lock since it sees that the lock is still owned by a client.
Updated by Jason Dillaman almost 8 years ago
- Status changed from In Progress to Fix Under Review
Updated by Jason Dillaman almost 8 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 8 years ago
- Copied to Backport #15712: jewel: Exclusive lock not properly released if journal non-primary added
Updated by Jason Dillaman almost 8 years ago
- Status changed from Pending Backport to Resolved
Actions