-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Bug fix for 'wait' time to be in nanoseconds for consistency instead of microseconds #2044
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
Bug fix for 'wait' time to be in nanoseconds for consistency instead of microseconds #2044
Conversation
Test behaviour fixed in CASSANDRA-18086 plus another one-line bug fix in Clock.waitUntil(). patch by Benedict Elliott Smith
495250a to
ac006e5
Compare
ac006e5 to
98b2a59
Compare
| default LatencySelector write(double percentile) { return (read, write) -> write.get(percentile); } | ||
| default LatencySelector maxReadWrite(double percentile) { return (read, write) -> max(read.get(percentile), write.get(percentile)); } | ||
| } | ||
|
|
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.
Was this line break removal intentional?
| { | ||
| ContentionStrategy strategy = parseStrategy("min=0ms,max=10ms,random=uniform").strategy; | ||
| double total = 0; | ||
| int count = 1000; |
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.
Mocking sleep and time would allow measuring if it the calculations are precisely correct.
It's fine for now though.
|
Committed as f0ad7eadbeb3208e08a9339881931222fdab253b |
…che#2044) Adds the metrics in IndexContext and the tree view of the query's Plan to the log messages produced for slow SAI queries. There is a new system property named cassandra.sai.slow_query_log.execution_info_enabled to toggle this feature, which is enabled by default. This property can be changed dynamically at any time, without a restart. When SAI-specific information is added to the slow query logger, the log messages for slow queries can take up almost 10x the (uncompressed) disk space. In the worst of the worst cases, with all queries being permanently slower than 500ms, and at least 50 different queries, reporting every 5 seconds (the default), the slow query logger can produce around 120MB of text per day and instance. With the detailed logging, it would be 1.14GB per day.
… logger (apache#2044) Adds the metrics in IndexContext and the tree view of the query's Plan to the log messages produced for slow SAI queries. There is a new system property named cassandra.sai.slow_query_log.execution_info_enabled to toggle this feature, which is enabled by default. This property can be changed dynamically at any time, without a restart. When SAI-specific information is added to the slow query logger, the log messages for slow queries can take up almost 10x the (uncompressed) disk space. In the worst of the worst cases, with all queries being permanently slower than 500ms, and at least 50 different queries, reporting every 5 seconds (the default), the slow query logger can produce around 120MB of text per day and instance. With the detailed logging, it would be 1.14GB per day.
CASSANDRA-18086