Project

General

Profile

Actions
Copy link

Subtask #16544

open

Feature #16540: rbd-mirror: support multiple peers per pool in mesh topology

rbd-mirror multi-peer: image deleter should only schedule deletion if last known primary image was deleted

Added by Jason Dillaman almost 8 years ago. Updated over 7 years ago.

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

0%

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

Description

The image deleter currently takes a shortcut since it only has to handle a single peer. With multiple peers, the image deleter should only execute if the local image's last tag was owned by the remote peer who just deleted the image.

Actions
Copy link
 #1

Updated by Jason Dillaman almost 8 years ago

  • Tracker changed from Bug to Subtask
Actions
Copy link
 #2

Updated by Jason Dillaman over 7 years ago

  • Subject changed from rbd-mirror: image deleter should only schedule deletion if last known primary image was deleted to rbd-mirror multi-peer: image deleter should only schedule deletion if last known primary image was deleted
Actions
Copy link

Also available in: Atom PDF