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

Verify correct ownership of attached locations on disk at C* startup

    XMLWordPrintableJSON

Details

    Description

      There's two primary things related to startup and disk ownership we should mitigate.

      First, an instance can come up with an incorrectly mounted volume attached as its configured data directory. This causes the wrong system tables to be read. If the instance which was previously using the volume is also down, its token could be taken over by the instance coming up.

      Secondly, in a JBOD setup, the non-system keyspaces may reside on a separate volume to the system tables. In this scenario, we need to ensure that all directories belong to the same instance, and that as the instance starts up it can access all the directories it expects to be able to. (including data, commit log, hints and saved cache dirs)

       

      Attachments

        Activity

          People

            jmckenzie Josh McKenzie
            jmckenzie Josh McKenzie
            Josh McKenzie
            Caleb Rackliffe
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: