Bug #46275
Cancellation of on-going scrubs
0%
Description
Although it's possible to prevent initiating new scrubs, we don't have a facility for terminating already on-going ones:
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2014-April/038488.html.
The problem pops up during maintenance of large deployments. Their huge size translates into small chance that all PGs are active+clean which affects e.g. upgrades. The ultimate outcome is unnecessary prolongation of maintenance windows.
The issue has been recently risen by Sergii Golovatiuk.
Related issues
History
#1 Updated by Radoslaw Zarzynski about 3 years ago
- Description updated (diff)
#2 Updated by Neha Ojha about 3 years ago
- Related to Feature #41363: Allow user to cancel scrub requests added
#3 Updated by David Zafman about 3 years ago
- Status changed from New to In Progress
#4 Updated by David Zafman about 3 years ago
We may be able to easily terminate scrubbing in between chunks if the noscrub/nodeep-scrub get set.
I will test this.
#5 Updated by David Zafman about 3 years ago
- Assignee set to David Zafman
#6 Updated by David Zafman about 3 years ago
- Related to Feature #46379: Add a force-scrub commands to bump already running scrubs added
#7 Updated by David Zafman about 3 years ago
- Pull request ID set to 35909
#8 Updated by David Zafman about 3 years ago
- Status changed from In Progress to Fix Under Review
#9 Updated by Neha Ojha about 3 years ago
- Backport set to nautilus,octopus
#10 Updated by David Zafman about 3 years ago
- Status changed from Fix Under Review to Pending Backport
#11 Updated by David Zafman about 3 years ago
- Copied to Backport #46706: nautilus: Cancellation of on-going scrubs added
#12 Updated by David Zafman about 3 years ago
- Copied to Backport #46707: octopus: Cancellation of on-going scrubs added
#13 Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
#14 Updated by David Zafman almost 3 years ago
- Related to Bug #47767: octopus: setting noscrub crashed osd process added