-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Always stop the timer when profiling the fetch phase #132570
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
Conversation
If setNextReader in any sub fetch phase throws we will not stop the profile timer we started. Subphases do various things in setNextReader from validations, throwing Exceptions outright, to reading Lucene specific things like doc values. This moves the timer.stop call in a finally block to make sure everything timer related is copacetic.
|
Hi @andreidan, I've created a changelog YAML for you. |
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
|
Reproduced the error, without this fix using: : Once this PR is in we will be able to see the real source of the problem (that's now being masked by this timer thing due to the try - finally block in |
nik9000
left a comment
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.
It'll help! It looks like there's some other bug hiding behind this one that we were eating by throwing the profiling exception here. Exciting! Let's merge this and see!
💔 Backport failed
You can use sqren/backport to manually backport by running |
If setNextReader in any sub fetch phase throws we will not stop the profile timer we started. Subphases do various things in setNextReader from validations, throwing Exceptions outright, to reading Lucene specific things like doc values. This moves the timer.stop call in a finally block to make sure everything timer related is copacetic.
If setNextReader in any sub fetch phase throws we will not stop the profile timer we started. Subphases do various things in setNextReader from validations, throwing Exceptions outright, to reading Lucene specific things like doc values. This moves the timer.stop call in a finally block to make sure everything timer related is copacetic.
If setNextReader in any sub fetch phase throws we will not stop the profile timer we started. Subphases do various things in setNextReader from validations, throwing Exceptions outright, to reading Lucene specific things like doc values.
This moves the timer.stop call in a finally block to make sure everything timer related is copacetic.
Relates to #132128