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

Null status entries on nodes that crash during decommission of a different node

    XMLWordPrintableJSON

Details

    • Normal

    Description

      This issue is reproducible through a Jepsen test of materialized views that crashes and decommissions nodes throughout the test.

      In a 5 node cluster, if a node crashes at a certain point (unknown) during the decommission of a different node, it may start with a null entry for the decommissioned node like so:
      DN 10.0.0.5 ? 256 ? null rack1

      This entry does not get updated/cleared by gossip. This entry is removed upon a restart of the affected node.

      This issue is further detailed in ticket 10068.

      Attachments

        1. n1.log
          586 kB
          Joel Knighton
        2. n2.log
          192 kB
          Joel Knighton
        3. n3.log
          618 kB
          Joel Knighton
        4. n4.log
          456 kB
          Joel Knighton
        5. n5.log
          838 kB
          Joel Knighton

        Issue Links

          Activity

            People

              jkni Joel Knighton
              jkni Joel Knighton
              Joel Knighton
              Stefania Alborghetti
              Joel Knighton Joel Knighton
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: