Project

General

Profile

Actions
Copy link

Bug #15709

closed

Exclusive lock not properly released if journal non-primary

Added by Jason Dillaman about 8 years ago. Updated almost 8 years ago.

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.

Related issues 1 (0 open — 1 closed)

Copied to rbd - Backport #15712: jewel: Exclusive lock not properly released if journal non-primaryResolvedJason DillamanActions
Actions
Copy link

Also available in: Atom PDF