Feature #24226
closedImage remove state machine should move image to trash as first step
0%
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.
Updated by Mahati Chamarthy over 5 years 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'?
Updated by Jason Dillaman over 5 years 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.