-
Notifications
You must be signed in to change notification settings - Fork 3.8k
CASSANDRA-16850 - Add client warnings and abort to tombstone and coordinator reads which go past a low/high watermark #1136
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
test/distributed/org/apache/cassandra/distributed/impl/InstanceMetrics.java
Outdated
Show resolved
Hide resolved
|
working on patch to make it so we can disable this behavior (leaving as default in 4.1 release for now) |
36f4e53 to
5413904
Compare
| DataLimits limits, | ||
| DataRange dataRange, | ||
| IndexMetadata index) | ||
| int digestVersion, |
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.
only fixed the formatting here.
| String msg = tombstoneAbortMessage(warnings.tombstoneAborts.get(), warnings.maxTombstoneAbortsCount.get(), command.toCQLString()); | ||
| ClientWarn.instance.warn(msg + " with " + command.loggableTokens()); | ||
| logger.warn(msg); | ||
| cfs().metric.clientTombstoneAborts.mark(); |
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.
should we inc if the query doesn't fail? kinda think we should inc at the throws?
…dinator reads which go past a low/high watermark
…onstanly hitting a vioalite variable
…s if it was still enabled
… as its already done in command.trackWarnings
…WarningsEnabled, so now we respect coordinator
e8d72c8 to
32da745
Compare
No description provided.