Project

General

Profile

Feature #24226

Image remove state machine should move image to trash as first step

Added by Jason Dillaman about 1 year ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
05/22/2018
Due date:
% Done:

0%

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

Description

... if the cluster minimum client release is set to luminous or later (i.e. trash is guaranteed to be supported). This will help resolve some of the race conditions where you can start deleting an image but another client can open the image and start writing to the image while it's being deleted.

History

#1 Updated by Mahati Chamarthy 9 months ago

Jason Dillaman wrote:

... if the cluster minimum client release is set to luminous or later (i.e. trash is guaranteed to be supported). This will help resolve some of the race conditions where you can start deleting an image but another client can open the image and start writing to the image while it's being deleted.

and hold them there until 'rbd trash purge' is called? Equivalent to making this config option "rbd_move_to_trash_on_remove" default to 'true'?

#2 Updated by Jason Dillaman 9 months ago

@Mahati: it would first move the image to the trash unconditionally and then if "rbd_move_to_trash_on_remove == false" it would proceed to delete it from the trash.

#3 Updated by Jason Dillaman 6 months ago

  • Status changed from New to Resolved

Also available in: Atom PDF