Project

General

Profile

Subtask #14417

Feature #11766: rbd-mirror: basic structure

Interlock RBD mirroring daemon and acquiring exclusive lock

Added by Jason Dillaman over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

If a local librbd client attempts to acquire the exclusive lock when the previous epoch was owned by a different cluster, this event must be interlocked with the mirroring daemon. If the daemon can register a new epoch in all known peers (prepare, commit/revert), it will be safe to continue the current mirroring period. If there is a conflict with a peer (a remote thinks it already owns that epoch), a new period should be started.

History

#1 Updated by Jason Dillaman over 4 years ago

Basic support for interlock is include in branch for #15232

#2 Updated by Jason Dillaman about 4 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF