[CASSANDRA-5768] If a Seed can't be contacted, a new node comes up as a cluster of 1

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.7, 2.0 beta 2
• Severity: Low
• Assignee: Brandon Williams Assign to me
• Reporter: Andy Cobley

Authors

Brandon Williams

Reviewers

Jason Brown

• Created: 17/Jul/13 12:51
• Updated: 16/Apr/19 09:32
• Resolved: 18/Jul/13 21:18

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: [e-mail]
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/