fix: corrupted rsources stats captured by processor for dropped jobs #3999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Using a unique job id instead of a zero (0) value for every dropped job so that stats are captured correctly.
Problem
By using the same (0) job id,
in_count
was being incremented for all different stat key combinations (job_run_id, task_run_id, source_id & destination_id), butfailed_count
was being erroneously incremented always for the first stat key, due to a corrupted jobIdsToStatKeyIndex.Linear Ticket
Resolves PIPE-433
Security