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

If a Seed can't be contacted, a new node comes up as a cluster of 1

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 1.2.7, 2.0 beta 2
    • None
    • None
    • Low

    Description

      Setting up a new test cluster using 2.0.0-beta1 and I noticed the following behaviour with vnodes turned on.

      I bring up one node all well and good. however if I bring up a second node, that can't contact the first (the first being the seed for the second) after a short period of time, the second goes ahead and assumes it's the only node and bootstraps with all tokens.

      NOTE also this email from Robert Coli
      To: user@cassandra.apache.org
      Obviously if you have defined a seed and cannot contact it, the node should not start as a cluster of one. I have a to-do list item to file a JIRA on the subject, but if you wanted to file and link us, that'd be super.

      Startup trace (from the can't contact the seed messages below).

      http://aep.appspot.com/display/ABcWltCES1srzPrj5CkS69-GB8o/

      Attachments

        1. cassandra.yaml
          29 kB
          Andy Cobley
        2. 5768.txt
          4 kB
          Brandon Williams

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            brandon.williams Brandon Williams Assign to me
            aecobley Andy Cobley
            Brandon Williams
            Jason Brown
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment