Project

General

Profile

Actions

Feature #61903

open

pybind/mgr/volumes: add config to turn off subvolume deletion

Added by Patrick Donnelly over 2 years ago. Updated 5 months ago.

Status:
Pending Backport
Priority:
High
Assignee:
Category:
Administration/Usability
Target version:
% Done:

0%

Source:
Development
Backport:
reef squid
Reviewed:
Affected Versions:
Component(FS):
mgr/volumes
Labels (FS):
task(easy), task(intern)
Pull request ID:
Tags (freeform):
backport_processed
Fixed In:
v20.0.0-442-ge56665c797
Released In:
v20.2.0~861
Upkeep Timestamp:
2025-11-01T00:58:32+00:00

Description

Sometimes we want to be able to turn off asynchronous subvolume deletion during cluster recovery scenarios. Add a config to turn the threads off.


Related issues 3 (2 open1 closed)

Related to CephFS - Feature #68630: mgr/vol: allow pausing cloner threadsPending BackportRishabh Dave

Actions
Copied to CephFS - Backport #70461: reef: pybind/mgr/volumes: add config to turn off subvolume deletionResolvedRishabh DaveActions
Copied to CephFS - Backport #70462: squid: pybind/mgr/volumes: add config to turn off subvolume deletionQA TestingRishabh DaveActions
Actions #1

Updated by Patrick Donnelly over 2 years ago

  • Tracker changed from Bug to Feature
Actions #2

Updated by Venky Shankar over 2 years ago

Patrick Donnelly wrote:

Sometimes we want to be able to turn off asynchronous subvolume deletion during cluster recovery scenarios. Add a config to turn the threads off.

Maybe add functionality to scale down the purge threads and then setting it to 0 would disable async purge.

Also, how about doing the same for async threads? Those are heavy on the file system too.

Actions #3

Updated by Patrick Donnelly over 2 years ago

Venky Shankar wrote:

Patrick Donnelly wrote:

Sometimes we want to be able to turn off asynchronous subvolume deletion during cluster recovery scenarios. Add a config to turn the threads off.

Maybe add functionality to scale down the purge threads and then setting it to 0 would disable async purge.

I'm not a fan of doing that because "restoring" the setting to a sane default is left to the admin who doesn't know better.

Also, how about doing the same for async threads? Those are heavy on the file system too.

You mean the cloner threads? i thought we already have a config for that.

Actions #4

Updated by Venky Shankar over 2 years ago

Patrick Donnelly wrote:

Venky Shankar wrote:

Patrick Donnelly wrote:

Sometimes we want to be able to turn off asynchronous subvolume deletion during cluster recovery scenarios. Add a config to turn the threads off.

Maybe add functionality to scale down the purge threads and then setting it to 0 would disable async purge.

I'm not a fan of doing that because "restoring" the setting to a sane default is left to the admin who doesn't know better.

Also, how about doing the same for async threads? Those are heavy on the file system too.

You mean the cloner threads? i thought we already have a config for that.

I meant supporting turning it off (by setting it to zero).

Actions #5

Updated by Patrick Donnelly over 2 years ago

  • Assignee deleted (Patrick Donnelly)
Actions #6

Updated by Venky Shankar over 2 years ago

  • Assignee set to Rishabh Dave

Rishabh, please take this one.

Actions #7

Updated by Venky Shankar over 2 years ago

From GChat

Rishabh Dave, 1:40 PM
https://tracker.ceph.com/issues/61903
Should I add an option to turn off threading or add an option to allow specifying number of thread user wants?

Right - an option that disables async subvolume deletion. As Patrick mentioned in note-3, there isn't a need to allow scaling the number of purge threads.

Actions #8

Updated by Venky Shankar over 2 years ago

Venky Shankar wrote:

From GChat

Rishabh Dave, 1:40 PM
https://tracker.ceph.com/issues/61903
Should I add an option to turn off threading or add an option to allow specifying number of thread user wants?

Right - an option that disables async subvolume deletion. As Patrick mentioned in note-3, there isn't a need to allow scaling the number of purge threads.

Rishabh, another point to add to this - One the operator disables async subvolume deletions, there needs to be a way for the operator to check if the purge threads have backed out performing the deletes and nothing related to async deletions are in-progress. This is required IMO as disabling async deletions is essentially asking the purge threads to voluntarily back-out doing purges.

Actions #9

Updated by Rishabh Dave about 2 years ago

  • Status changed from New to Fix Under Review
Actions #10

Updated by Patrick Donnelly almost 2 years ago

Where is the fix that is under review? @Rishabh Dave

Actions #11

Updated by Patrick Donnelly almost 2 years ago

  • Target version changed from v19.0.0 to v20.0.0
Actions #12

Updated by Konstantin Shalygin over 1 year ago

  • Backport changed from reef,quincy,pacific to reef,quincy
Actions #13

Updated by Rishabh Dave over 1 year ago

  • Pull request ID set to 54396
Actions #14

Updated by Konstantin Shalygin about 1 year ago

  • Backport changed from reef,quincy to reef
Actions #15

Updated by Konstantin Shalygin about 1 year ago

  • Backport changed from reef to reef squid
Actions #16

Updated by Venky Shankar about 1 year ago

  • Status changed from Fix Under Review to Pending Backport
Actions #17

Updated by Venky Shankar about 1 year ago

  • Related to Feature #68630: mgr/vol: allow pausing cloner threads added
Actions #18

Updated by Upkeep Bot about 1 year ago

  • Copied to Backport #70461: reef: pybind/mgr/volumes: add config to turn off subvolume deletion added
Actions #19

Updated by Upkeep Bot about 1 year ago

  • Copied to Backport #70462: squid: pybind/mgr/volumes: add config to turn off subvolume deletion added
Actions #20

Updated by Upkeep Bot about 1 year ago

  • Tags (freeform) set to backport_processed
Actions #21

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to e56665c7977020f5edb3aed643dca867fe93e656
  • Fixed In set to v20.0.0-442-ge56665c7977
  • Upkeep Timestamp set to 2025-07-09T16:43:47+00:00
Actions #22

Updated by Upkeep Bot 8 months ago

  • Fixed In changed from v20.0.0-442-ge56665c7977 to v20.0.0-442-ge56665c797
  • Upkeep Timestamp changed from 2025-07-09T16:43:47+00:00 to 2025-07-14T17:41:55+00:00
Actions #23

Updated by Upkeep Bot 5 months ago

  • Released In set to v20.2.0~861
  • Upkeep Timestamp changed from 2025-07-14T17:41:55+00:00 to 2025-11-01T00:58:32+00:00
Actions

Also available in: Atom PDF