Better concurrency control for upload scheduling
Bug #818855 reported by
Tristan Seligmann
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Entropy Object Store |
New
|
Medium
|
Unassigned | ||
Bug Description
Bug #818854 address one possible cause of an upload scheduling meltdown. However, if a backend is down or otherwise unreachable for a sufficient period of time, there will still be a significant backlog of scheduled uploads; even though these will most likely not be scheduled for exactly the same time, there will likely be a significant number of uploads running concurrently, which could cause sufficient resource starvation to achieve meltdown, and is most likely undesirable even when it does not lead to a complete meltdown.
The correct approach for handling this is probably to control concurrency independently for each backend.
Related branches
lp:~fusion-developers/entropy-store/818855-limit-upload-scheduler
- Fusion Developers: Pending requested
-
Diff: 428 lines (+324/-23)2 files modifiedentropy/store.py (+91/-22)
entropy/test/test_store.py (+233/-1)
| Changed in entropy-store: | |
| importance: | Undecided → Medium |
To post a comment you must log in.
