cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12587) Log when there is a timestamp tie that is being broken
Date Thu, 01 Sep 2016 17:37:20 GMT


Jason Brown commented on CASSANDRA-12587:


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:
>             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

View raw message