Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] Skip claiming tasks that were modified during the task claiming phase (#198711) #199251

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.x:

Questions ?

Please refer to the Backport tool documentation

…elastic#198711)

Resolves elastic#196300

In this PR, I'm removing the fallback we had when `startedAt` value is
missing (elastic#194759) in favour of
dropping the task document from the claiming cycle. The additional logs
that were added showed that tasks that were missing a `startedAt` value
was because they were being re-created during the exact same time they
were being claimed, causing the task to have an `idle` status and a
missing `startedAt` value. Given the scenario, it feels better to drop
them from getting claimed and to instead try again at the next claim
cycle where the race condition shouldn't occur.

(cherry picked from commit a19dd8e)
@kibanamachine kibanamachine merged commit 4e8b6ec into elastic:8.x Nov 7, 2024
33 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @mikecote

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants