CNDB-14261: Separate timeout for aggregation queries (#1741) #1775
Conversation
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
|
https://github.com/riptano/cndb/13770 does not exist |
CNDB-13770 is Separate timeout for aggregation queries (#1741) In CC, aggregate user queries use the same range read timeout. In DSE, we had a separate timeout that defaulted to 120s. We would like to retain that functionality. In addition, aggregate queries in metrics look just like range reads. We'd like to distinguish them. This PR adds a separate 120s timeout for aggregate queries. The timeout is configurable with `aggregation_request_timeout_in_ms` Config parameter
jakubzytka
force-pushed
the
cndb-main-release-202501-cndb-13770-hotfix
branch
from
137fdcc to
8731204
Compare
jakubzytka
changed the title
|
❌ Build ds-cassandra-pr-gate/PR-1775 rejected by Butler5 new test failure(s) in 3 builds Found 5 new test failures
Found 7 known test failures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is the issue
In CC, aggregate user queries use the same range read timeout. In DSE,
we had a separate timeout that defaulted to 120s. We would like to
retain that functionality.
In addition, aggregate queries in metrics look just like range reads.
We'd like to distinguish them.
What does this PR fix and why was it fixed
This PR adds a separate 120s timeout for aggregate queries. The timeout
is configurable with
aggregation_request_timeout_in_msConfigparameter
What is the issue
...
What does this PR fix and why was it fixed
...