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

dtests that involve topology changes should verify system.peers on all nodes

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • 2.1.x
    • Test/dtest/python
    • None

    Description

      This is especially true for replace where I've discovered it's wrong in 1.2.19, which is sad because now it's too late to fix. We've had a lot of problems with incorrect/null system.peers, so after any topology change we should verify it on every live node when everything is finished.

      Attachments

        Issue Links

          Is contained by

          Task - A task that needs to be done. CASSANDRA-9012 Triage missing test coverage

          • Normal -
          • Open
          is depended upon by

          Improvement - An improvement or enhancement to an existing feature or task. CASSANDRA-8304 Explore evicting replacement state sooner

          • Normal -
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-9180 Failed bootstrap/replace attempts persist entries in system.peers

          • Normal -
          • Resolved

          Activity

            People

              enigmacurry Ryan McGuire
              brandon.williams Brandon Williams
              Ryan McGuire
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: