Feature #543
closedPG::search_for_missing: don't iterate over all missing
0%
Description
PG::search_for_missing processes a replica's missing map to determine if it has any objects that we need.
If the missing set becomes very large, this could get very time-consuming. Instead, we probably want to just iterate over our unfound set. (Objects we know about but don't know where to find.)
This would involve tracking the unfound set separately (need a fast way to iterate over that). It also involves changing the retry logic in pull so that we can figure out some new locations to pull from when pulling from the first location fails. After all, the whole reason we try to find every location now is because pulling from some of them may not work (in theory.)
This seems fairly low priority but I'm making a note.
Updated by Sage Weil over 13 years ago
- Estimated time set to 8:00 h
- Source set to 5
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
363) - Translation missing: en.field_position set to 842
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
850) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 860
Updated by Loïc Dachary over 9 years ago
- Status changed from New to Resolved
The code base changed significantly and does not have this problem anymore.