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

Make TokenMetadata's ring version increments atomic

    XMLWordPrintableJSON

Details

    • Correctness - Recoverable Corruption / Loss
    • Normal
    • Normal
    • Code Inspection
    • All
    • None
    • Hide

      The patch adds a test that would be almost guaranteed to fail if the ring invalidation ever became unsafe.

      Show
      The patch adds a test that would be almost guaranteed to fail if the ring invalidation ever became unsafe.

    Description

      The update semantics of the ring version in TokenMetadata are not clear. The instance variable itself is volatile, but it is still incremented by a non-atomic check-and-set, and not all codepaths do that while holding the TokenMetadata write lock. We could make this more intelligible by forcing the external callers to use both the write when invalidating the ring and read lock when reading the current ring version. Most of the readers of the ring version (ex. compaction) don't need it to be fast, but it shouldn't be a problem even if they do. If we do this, we should be able to avoid a situation where concurrent invalidations don't produce two distinct version increments.

      Attachments

        Activity

          People

            maedhroz Caleb Rackliffe
            maedhroz Caleb Rackliffe
            Caleb Rackliffe
            Andres de la Peña, Yifan Cai
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 2h
                2h