Feature #18206
closed
osd: osd_scrub_during_recovery only considers primary, not replicas
Added by Sage Weil over 7 years ago.
Updated over 6 years ago.
Description
We should also avoid scrubbing if the replica is busy doing recovery. That means the scrub scheduler should decline the reservation, probably, but we need to verify that some timed backoff is in place.
- Tracker changed from Bug to Feature
- Project changed from Ceph to RADOS
- Category set to Scrub/Repair
- Component(RADOS) OSD added
- Status changed from 12 to In Progress
- Assignee set to David Zafman
- Backport set to jewel, luminous
david, i just read your inquiry over IRC. what would you want me to review for this ticket? do we have a PR for it already?
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #21077: luminous: osd: osd_scrub_during_recovery only considers primary, not replicas added
- Backport changed from jewel, luminous to jewel
Thanks Nathan. I think some issue and it did not create a tracker for jewel backport so I removed luminous so it can create for jewel.
- Backport changed from jewel to jewel, luminous
@Vikhyat Umrao, I think Abhi just created the luminous backport tracker manually. The jewel one will be created automagically when I next run the script.
- Copied to Backport #21117: jewel: osd: osd_scrub_during_recovery only considers primary, not replicas added
Nathan Cutler wrote:
@Vikhyat Umrao, I think Abhi just created the luminous backport tracker manually. The jewel one will be created automagically when I next run the script.
Thanks Nathan.
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF