-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Add note on troubleshooting laggy cancellations #97485
Add note on troubleshooting laggy cancellations #97485
Conversation
Today we document that tasks may not react to cancellations immediately, but in practice it's surprising to users and kind of a bug if they run for too long after being cancelled. This commit adds a little extra detail about the information to collect to troubleshoot such a situation.
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-distributed (Team:Distributed) |
complete promptly, use the list tasks API with the `?detailed` parameter to | ||
identify the other tasks the system is running and also use the | ||
<<cluster-nodes-hot-threads>> API to obtain detailed information about the work | ||
the system is doing instead of processing the cancellation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe instead of the cancelled task being completed
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++ good point, see 78f3b1f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Today we document that tasks may not react to cancellations immediately, but in practice it's surprising to users and kind of a bug if they run for too long after being cancelled. This commit adds a little extra detail about the information to collect to troubleshoot such a situation.
Today we document that tasks may not react to cancellations immediately, but in practice it's surprising to users and kind of a bug if they run for too long after being cancelled. This commit adds a little extra detail about the information to collect to troubleshoot such a situation.
Today we document that tasks may not react to cancellations immediately, but in practice it's surprising to users and kind of a bug if they run for too long after being cancelled. This commit adds a little extra detail about the information to collect to troubleshoot such a situation.
Today we document that tasks may not react to cancellations immediately, but in practice it's surprising to users and kind of a bug if they run for too long after being cancelled. This commit adds a little extra detail about the information to collect to troubleshoot such a situation.
Today we document that tasks may not react to cancellations immediately,
but in practice it's surprising to users and kind of a bug if they run
for too long after being cancelled. This commit adds a little extra
detail about the information to collect to troubleshoot such a
situation.