If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Prioritise log parsing of failed jobs over successful ones

NEW
Unassigned

Status

Tree Management
Treeherder: Log Parsing & Classification
P4
normal
3 years ago
14 days ago

People

(Reporter: emorley, Unassigned)

Tracking

Details

(Reporter)

Description

3 years ago
Broken out from bug 1074927.

We need to:
1) Double check that we are correctly giving higher priority to log parsing tasks for jobs that are failed, vs ones that were successful.
2) Add a cut-off time (or something similar), such that even a successful job won't have to wait longer than N minutes before being parsed (to prevent a backlog from suppressing log parsing of successful jobs indefinitely). This will help with Joel's use-case in bug 1075641.
(Reporter)

Updated

3 years ago
Priority: P1 → P2
(Reporter)

Updated

3 years ago
Blocks: 1080757
No longer blocks: 1059400
(Reporter)

Updated

3 years ago
No longer blocks: 1080757
Component: Treeherder → Treeherder: Data Ingestion
(Reporter)

Comment 1

3 years ago
It turns out the log_parser, log_parser_hp and log_parser_fail queues are equal priority, and supposedly dealt with in a round robin manner.

It would help with backlogs if we prioritised log_parser_hp and log_parser_fail over log_parser.

Perhaps we should rebalance some of the queues once the default queue has been split up. We could also try adding some of the high priority queues to more than one node type (eg log_parser_hp and high_priority could be done by any of {etl,processor} etc).
(Reporter)

Updated

3 years ago
Summary: Check/adjust log parsing prioritisation of failed jobs over successful ones → Prioritise log parsing of failed jobs over successful ones
(Reporter)

Updated

3 years ago
Priority: P2 → P4
(Reporter)

Updated

3 years ago
Blocks: 1152742
(Reporter)

Updated

14 days ago
Component: Treeherder: Data Ingestion → Treeherder: Log Parsing & Classification
You need to log in before you can comment on or make changes to this bug.