Actions
Bug #54435
closedbucket index completions may not retry after reshard
% Done:
100%
Source:
Development
Tags:
reshard backport_processed
Backport:
octopus pacific quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
the RGWIndexCompletionThread stores a list of index completion ops that failed with ERR_BUSY_RESHARDING, for synchronous retry under guard_reshard() in RGWIndexCompletionThread::process()
however, after process() finishes it's work, it goes to sleep on its condition variable without checking for more completions. so it's easy for RGWIndexCompletionThread to miss signals on this condition variable, and not wake up even though there's still work to do. once completions are stalled this way, nothing will wake up the thread again until new completions race with another reshard
Updated by Casey Bodley about 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 45212
Updated by Casey Bodley about 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 2 years ago
- Copied to Backport #54496: quincy: bucket index completions may not retry after reshard added
Updated by Backport Bot about 2 years ago
- Copied to Backport #54497: pacific: bucket index completions may not retry after reshard added
Updated by Backport Bot about 2 years ago
- Copied to Backport #54498: octopus: bucket index completions may not retry after reshard added
Updated by Backport Bot over 1 year ago
- Tags changed from reshard to reshard backport_processed
Updated by Konstantin Shalygin 4 months ago
- Status changed from Pending Backport to Resolved
- Assignee set to Casey Bodley
- % Done changed from 0 to 100
- Source set to Development
Actions