-
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 manager can get in an endless loop when attempting to claim non-saved object tasks #51222
Comments
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
@ash9146 to solve the issue, the objects without |
@mikecote Thanks. I solved |
Hello , this is not resolve the problem for me ElasticStack version : 7.7.0 |
Hi @wixaw Could you expand a bit about your setup? Are there any other errors in the logs that might give a hint to what's going on? |
Hello @gmmorris This is only in the logs, I wanted to discover the free alert system in the kibana logs and if we have to manage events in this one, it is rather a problem to have these false alerts. This alert appears approximately every 15 seconds without ever stopping. Thank you |
Hello @gmmorris |
Sorry, I'm a little confused - are we talking about an alert or an error in the logs? In fact, if you're seeing this in 7.9 then I suspect it's unrelated to the the original issue mentioned here... 🤔 |
With the new system of free alerts in kibana, I want parse logs in python.
I have this tasks
|
Hi @wixaw , I'd recommend against using the kibana log in this manner. As you've found, the Kibana log can get quite noisy and this is going to make it harder for you to act on the alerted instances. As you have found, the log included a lot more than just the results of alerting, but rather everything that gets logged, including errors (which is what seems to be making things difficult for you right now :)). Top be clear, these aren't false positives, they are simply unrelated to your alerts. Instead of using the |
It seems possible when users upgrade to 7.4 that an old version of Kibana re-inserts tasks within the
.kibana_task_manager
index without the id prefix oftask:
. When this scenario happens, task manager would get in an infinite loop attempting to claim those tasks but doing the update call on the object containing the prefix (task:
).For example, a task with id of
oss_telemetry-vis_telemetry
would cause task manager to attempt claiming a task with an id oftask:oss_telemetry-vis_telemetry
. This would cause a 409 to be returned since the version returned on read doesn't match the document version of the other.In 7.4, it would cause for example 200 update requests per second of attempting to claim a task while constantly getting a 409 as a result. In 7.5 the issue isn't as severe but every 30 seconds a log like this shows up:
[error][task_manager] Failed to mark Task vis_telemetry "oss_telemetry-vis_telemetry" as running: Task has been claimed by another Kibana service
.We should make sure when searching / claiming tasks that we also make sure they're saved objects. Similar to how the migrator only migrates documents that are saved objects: https://github.com/elastic/kibana/blob/master/src/core/server/saved_objects/migrations/core/migrate_raw_docs.ts#L41.
Could be similar to a 7.1 issue? #47607
The text was updated successfully, but these errors were encountered: