action #98922
closed
openQA Project (public) - coordination #64746: [saga][epic] Scale up: Efficient handling of large storage to be able to run current tests efficiently but keep big archives of old results
openQA Project (public) - coordination #80546: [epic] Scale up: Enable to store more results
coordination #96974: [epic] Improve/reconsider thresholds for skipping cleanup
Run asset cleanup concurrently to results based on config
Added by mkittler over 3 years ago.
Updated about 3 years ago.
Description
motivation¶
see #96974
acceptance criteria¶
- AC1: A configuration option exists to allow asset and result cleanup concurrently.
suggestions¶
- Make the acquisition of the
limit_tasks lock depended on a config value in limit tasks for assets and results.
- Status changed from New to In Progress
- Due date set to 2021-10-05
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
- Tracker changed from coordination to action
- Status changed from Feedback to Resolved
I just triggered a cleanup job in production and had a look at the locks. Looks like it works.
- Due date deleted (
2021-10-05)
- Copied to action #103954: Run asset cleanup concurrently to results based on config on o3 as well added
Also available in: Atom
PDF