Feature #2826
closed
osd: backfill target reservations
Added by Sage Weil almost 12 years ago.
Updated over 11 years ago.
Description
When osds are marked out, the recovery ops per primary throttling works fine, because the backfill targets tend to be spread all over.
When you mark an osd in, there tends to be a single backfill target. The larger the cluster, the larger the number of primary osds who are trying to send it data.
I think we need to use a reservation system similar to what we do for scrubbing so that there are configurable number of backfills targetting a single OSD.
- Description updated (diff)
- Translation missing: en.field_story_points set to 13
- Translation missing: en.field_position deleted (
4)
- Translation missing: en.field_position set to 2
- Translation missing: en.field_position deleted (
29)
- Translation missing: en.field_position set to 1
- Priority changed from Normal to High
- Tags set to CY2012
- Target version set to v0.53c
- Translation missing: en.field_position deleted (
20)
- Translation missing: en.field_position set to 1
- Assignee set to Samuel Just
- Target version changed from v0.53c to v0.54a
- Translation missing: en.field_position deleted (
19)
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 1407
- Status changed from New to Resolved
- Translation missing: en.field_position deleted (
1406)
- Translation missing: en.field_position set to 3
- Translation missing: en.field_position deleted (
3)
- Translation missing: en.field_position set to 2
Also available in: Atom
PDF