You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Brown (JIRA)" <ji...@apache.org> on 2016/09/01 17:37:20 UTC
[jira] [Commented] (CASSANDRA-12587) Log when there is a timestamp
tie that is being broken
[ https://issues.apache.org/jira/browse/CASSANDRA-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456097#comment-15456097 ]
Jason Brown commented on CASSANDRA-12587:
-----------------------------------------
+1
Is it worthwhile to expose a metric, as well? I'm suspecting not (as, hopefully, it will always output zero), but just throwing out the idea for discussion.
> 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)