-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Don't generate stacktrace in TaskCancelledException #125002
Conversation
Pinging @elastic/es-search (Team:Search) |
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.
❤️
This should be marked as a bug IMO and this is a bug fix.
Hi @iverase, I've created a changelog YAML for you. |
Let's make it a bug then. |
For the record, this change does not hurt and it's a good idea, but after #118266 , where we removed stacktraces for all exceptions returned back to the coord node, I am not so sure it's going to practically make a huge difference. |
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
💔 Backport failed
You can use sqren/backport to manually backport by running |
# Conflicts: # modules/aggregations/src/internalClusterTest/java/org/elasticsearch/aggregations/bucket/SearchCancellationIT.java
…125031) * Don't generate stacktrace in TaskCancelledException (#125002) # Conflicts: # modules/aggregations/src/internalClusterTest/java/org/elasticsearch/aggregations/bucket/SearchCancellationIT.java * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
No need to expend cycles and heap on it.