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

Race in commit log replay can cause rejected mutations

    XMLWordPrintableJSON

Details

    • Availability - Process Crash
    • Normal
    • Normal
    • User Report
    • All
    • None
    • Hide

      A dtest is included

      Show
      A dtest is included

    Description

      We don't force order in the execution of replayed mutations and hence a mutation can move ahead of or behind a schema change it relies on (e.g. added/removed column), which can then cause it to be rejected because of a schema mismatch.

      To fix this, we need to identify schema mutations and make sure the log enforces their execution after all previous mutations have completed and before anything following is started.

      Schema mutations are flushed after being applied, so this only would be a problem if the node abruptly stops before flushing the schema mutation.

      Attachments

        Issue Links

          Activity

            People

              adelapena Andres de la Peña
              adelapena Andres de la Peña
              Andres de la Peña
              Berenguer Blasi, Jacek Lewandowski, Yifan Cai
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 3h 10m
                  3h 10m