Re: handling down node cassandra 2.0.15

On Wed, Nov 18, 2015 at 6:16 AM, Anuj Wadehra wrote: > Suppose, gc grace seconds=10days, max hinted handoff period=3 hrs, 3 nodes > are there A,B & C,RF =3 and my client is reading at CL ONE. C remains down > for 5 hours and misses many updates including those which

Re: handling down node cassandra 2.0.15

@Rob interesting something i will try next time, for step 3 you mentioned -- I just remove the -Dcassandra.join_ring=false option and restart the cassandra service? @Anuj, gc_grace_seconds dictates how long hinted handoff are stored right. These might be good where we explicitly delete values

Re: handling down node cassandra 2.0.15

ique data of node C. While repair is going on, node C will get all the Writes.  @Anishek Hinted handoffs are not related to gc grace seconds. Thanks Anuj Sent from Yahoo Mail on Android From:"Anishek Agarwal" <anis...@gmail.com> Date:Wed, 18 Nov, 2015 at 1:49 pm Subject:Re

Re: handling down node cassandra 2.0.15

Date:Tue, 17 Nov, 2015 at 10:52 am Subject:Re: handling down node cassandra 2.0.15 hey Anuj, Ok I will try that next time, so you are saying since i am replacing the machine in place(trying to get the same machine back in cluster) which already has some data, I dont clean the commitlogs/data dir

Re: handling down node cassandra 2.0.15

On Tue, Nov 17, 2015 at 4:33 AM, Anuj Wadehra wrote: > Only if gc_grace_seconds havent passed since the failure. If your machine > is down for more than gc_grace_seconds you need to delete the data > directory and go with auto bootstrap = true . > Since CASSANDRA-6961

RE: handling down node cassandra 2.0.15

25 AM To: user@cassandra.apache.org Subject: Re: handling down node cassandra 2.0.15 nope its not On Mon, Nov 16, 2015 at 5:48 PM, sai krishnam raju potturi <pskraj...@gmail.com<mailto:pskraj...@gmail.com>> wrote: Is that a seed node? On Mon, Nov 16, 2015, 05:21 Anishek Agarwal &

Re: handling down node cassandra 2.0.15

Is that a seed node? On Mon, Nov 16, 2015, 05:21 Anishek Agarwal wrote: > Hello, > > We are having a 3 node cluster and one of the node went down due to a > hardware memory failure looks like. We followed the steps below after the > node was down for more than the default

Re: handling down node cassandra 2.0.15

nope its not On Mon, Nov 16, 2015 at 5:48 PM, sai krishnam raju potturi < pskraj...@gmail.com> wrote: > Is that a seed node? > > On Mon, Nov 16, 2015, 05:21 Anishek Agarwal wrote: > >> Hello, >> >> We are having a 3 node cluster and one of the node went down due to a >>

Re: handling down node cassandra 2.0.15

2015 9:25 AM To: user@cassandra.apache.org Subject: Re: handling down node cassandra 2.0.15   nope its not   On Mon, Nov 16, 2015 at 5:48 PM, sai krishnam raju potturi <pskraj...@gmail.com> wrote: Is that a seed node?   On Mon, Nov 16, 2015, 05:21 Anishek Agarwal <anis...@gm

Re: handling down node cassandra 2.0.15

f_dead_node     From: Anishek Agarwal [mailto:anis...@gmail.com] Sent: Monday, November 16, 2015 9:25 AM To: user@cassandra.apache.org Subject: Re: handling down node cassandra 2.0.15   nope its not   On Mon, Nov 16, 2015 at 5:48 PM, sai krishnam raju potturi <pskraj...@gmail.com> wrote: Is

Re: handling down node cassandra 2.0.15

* user@cassandra.apache.org > *Subject:* Re: handling down node cassandra 2.0.15 > > > > nope its not > > > > On Mon, Nov 16, 2015 at 5:48 PM, sai krishnam raju potturi < > pskraj...@gmail.com> wrote: > > Is that a seed node? > > > > On Mo

Re: handling down node cassandra 2.0.15

address? That is usually the error I > get when I forget to set the replace_address on Cassandra-env. > > JVM_OPTS="$JVM_OPTS -Dcassandra.replace_address=address_of_dead_node > > > *From:* Anishek Agarwal [mailto:anis...@gmail.com] > *Sent:* Monday, November 16, 2015 9:25 AM > *To:*

handling down node cassandra 2.0.15

Hello, We are having a 3 node cluster and one of the node went down due to a hardware memory failure looks like. We followed the steps below after the node was down for more than the default value of *max_hint_window_in_ms* I tried to restart cassandra by following the steps @ 1.