Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-12587

Log when there is a timestamp tie that is being broken

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              brandon.williams Brandon Williams
            • Votes:
              4 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated: