[
https://issues.apache.org/jira/browse/CASSANDRA-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458343#comment-15458343
]
Jason Brown commented on CASSANDRA-12587:
-----------------------------------------
I was thinking that it might be easier to trigger a monitoring system alert
based on a metric going above zero, rather than simply monitoring logs. The log
would be more informational, for sure, with the CQL partition.
With or without a metric is fine with me, but the log entry I'm definitely +1 on
> Log when there is a timestamp tie that is being broken
> ------------------------------------------------------
>
> Key: CASSANDRA-12587
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12587
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
>
> When there is a timestamp tie, it can be very difficult to discern what has
> happened, since currently the columns will resolve individually by value.
> CASSANDRA-6123 would make this a bit more deterministic, but that would also
> make scenarios like this nearly impossible to troubleshoot. Since timestamp
> ties *should* be fairly rare, I propose we at least log the row key that had
> a tie so operators are aware that something that should almost never happen,
> is happening.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
