RE: Cassandra seems to replace existing node without specifying replace_address

2015-05-29 Thread Thomas Whiteway
auto_bootstrap is true (we don’t set it explicitly and that’s the default). We’re using vnodes and initial_token is explicitly set to null. Thomas From: Robert Coli [mailto:rc...@eventbrite.com] Sent: 28 May 2015 19:07 To: user@cassandra.apache.org Subject: Re: Cassandra seems to replace

Re: Cassandra seems to replace existing node without specifying replace_address

2015-05-28 Thread Robert Coli
On Thu, May 28, 2015 at 2:00 AM, Thomas Whiteway < thomas.white...@metaswitch.com> wrote: > Sorry, I should have been clearer. In this case we’ve decommissioned > the node and deleted the data, commitlog, and saved caches directories so > we’re not hitting CASSANDRA-8801. We also hit the “A nod

RE: Cassandra seems to replace existing node without specifying replace_address

2015-05-28 Thread Thomas Whiteway
, just not in 2.1.4. Thomas From: Robert Coli [mailto:rc...@eventbrite.com] Sent: 27 May 2015 20:41 To: user@cassandra.apache.org Subject: Re: Cassandra seems to replace existing node without specifying replace_address On Wed, May 27, 2015 at 5:48 AM, Thomas Whiteway mailto:thomas.white

Re: Cassandra seems to replace existing node without specifying replace_address

2015-05-27 Thread Robert Coli
On Wed, May 27, 2015 at 5:48 AM, Thomas Whiteway < thomas.white...@metaswitch.com> wrote: > I’ve been investigating using replace_address to replace a node that > hasn’t left the cluster cleanly and after upgrading from 2.1.0 to 2.1.4 it > seems that adding a new node will automatically replace a