-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Task remains in "running" state when last attempt timed out #79165
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
I've done some investigation and it looks like we can use the kibana/x-pack/plugins/task_manager/server/queries/mark_available_tasks_as_claimed.ts Lines 103 to 108 in a8b1b9e
|
Waiting on this issue until #80371 is investigated/resolved. My concern is that if there is some natural limit to the updateByQuery that is preventing older docs from being returned/updated/sorted, removing the clause to limit the search by |
It seems that we found the issue with the zombie idle tasks in TM, so we can proceed here. There's a proposed fix in PR #80692, I suspect it will not affect this issue, seems like we can merge the fixes independently. |
This is outlined in the documentation under limitations, just very strange once we have a Task Manager UI.
Steps to reproduce:
await new Promise(resolve => {});
.kibana_task_manager
document and once it reaches attempts: 3 (or 2?), you will see it remain inrunning
statusNOTE: The default timeouts and retry can be long, you can modify those in the task definition (to ex:
timeout: '10s'
) and in the task runner (to ex:30s
) for backoff multiple to test this.The text was updated successfully, but these errors were encountered: