Per T240518#5751630, newly defined jobs are processed as part of a catchall low_traffic_jobs group unless a separate queue is specifically defined for them via ChangeProp rule. This creates a risk of a misbehaving job blocking a large number of miscellaneous jobs, as seen recently with the misbehaving fetchGoogleCloudVisionAnnotation job.
Some possible ideas of how to improve the situation:
- Do not add jobs with release timestamps to the catchall group (throw an exception instead)
- Require explicitly registering jobs via ChangeProp rule, with review to ensure they are placed in the correct group
- Do not assume unknown new jobs will be low-traffic