QA » openQA Project

Motivation¶

#164979 alerted us about /results being nearly full. We found that groupless jobs are now the biggest offender linked to heavy jobs failing often triggering also heavy openqa-investigate jobs.

Acceptance criteria¶

• AC1: Big investigation jobs will not fill up our disk space; we would instead just keep less of them.

Suggestions¶

• Count investigation jobs towards the group of the original job
  • Investigation jobs are groupless to avoid being considered for the result of the according group
  • It is probably also not wanted by users; investigation jobs should not cause normal jobs to be stored less long but still be kept for a short time.
  • The way the cleanup algorithm currently works makes this also hard to implement. It goes though jobs group by group and factoring in groupless jobs here without good relations in the database is not straight forward / efficient.
• Use a dedicated group for all investigation jobs
  • Sounds most promising - just create a new group and schedule investigation jobs to be part of it.
  • There is a caveat: Having all investigation jobs in one group does not solve the problem that investigation jobs for a particular scenario become very big. If we put everything in one group one scenario might cause other investigation jobs to be stored only very shortly.