-
Notifications
You must be signed in to change notification settings - Fork 25.5k
ES|QL per-cluster took time is incorrectly calculated and causes fatal exceptions #115017
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
079c419
Intmd commit - Added 'mark' methods to EsqlExecutionInfo and being us…
quux00 041b002
Removed debugging lines
quux00 8a7a670
Now handling cases where took time is not present in the ComputeRersp…
quux00 e2b2283
Added test for updateExecutionInfoAtEndOfPlanning
quux00 d192d8f
Added testAcquireComputeCCSListenerWithComputeResponseFromOlderCluster
quux00 c43060f
Minor cleanup
quux00 9926c2d
PR feedback
quux00 446ff59
Merge remote-tracking branch 'elastic/main' into bug/esql-cluster-too…
quux00 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
74 changes: 48 additions & 26 deletions
74
...rc/internalClusterTest/java/org/elasticsearch/xpack/esql/action/CrossClustersQueryIT.java
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 we can use
timeValueNanos
for brevity?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.
Do you mean for
relativeStartNanos
? I prefer the term I used because it emphasizes that this is for relative time (duration) calculations only not related to wall clock time, which is the mental model block that resulted in this bug.And I took the term from TransportSearchAction.SearchTimeProvider to indicate it has the same function as that field. I considered using SearchTimeProvider here as well, but I haven't found a need for the
absoluteStartMillis
field in ESQL yet, so I just went with the single field option here.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.
No I mean using the method
TimeValue.timeValueNanos