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

system.peers table not updated after decommissioning nodes in C* 2.0

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 1.2.14, 2.0.5
    • Component/s: None
    • Labels:
      None
    • Environment:

      Datastax AMI running EC2 m1.xlarge instances

    • Severity:
      Normal
    • Since Version:

      Description

      After decommissioning my cluster from 20 to 9 nodes using opscenter, I found all but one of the nodes had incorrect system.peers tables.

      This became a problem (afaik) when using the python-driver, since this queries the peers table to set up its connection pool. Resulting in very slow startup times, because of timeouts.

      The output of nodetool didn't seem to be affected. After removing the incorrect entries from the peers tables, the connection issues seem to have disappeared for us.

      Would like some feedback on if this was the right way to handle the issue or if I'm still left with a broken cluster.

      Attached is the output of nodetool status, which shows the correct 9 nodes. Below that the output of the system.peers tables on the individual nodes.

        Attachments

        1. peers
          8 kB
          Guyon Moree
        2. 6053-v1.patch
          8 kB
          Tom Hobbs

          Activity

            People

            • Assignee:
              thobbs Tom Hobbs
              Reporter:
              gumuz Guyon Moree
              Authors:
              Tom Hobbs
              Reviewers:
              Brandon Williams
            • Votes:
              9 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: