cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anishek Agarwal <anis...@gmail.com>
Subject Re: handling down node cassandra 2.0.15
Date Wed, 18 Nov 2015 08:18:51 GMT
@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 from the table. we
just have ttl and DTCS should delete data older than 1 month. In this case
do i need to wipe the node and then start copy of key space again ? or can
i run a repair once it joins the right with auto_bootstrap=false.



On Wed, Nov 18, 2015 at 1:20 AM, Robert Coli <rcoli@eventbrite.com> wrote:

> On Tue, Nov 17, 2015 at 4:33 AM, Anuj Wadehra <anujw_2003@yahoo.co.in>
> 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 you can :
>
> 1) bring up the node with join_ring=false
> 2) repair it
> 3) join it to the cluster
>
> https://issues.apache.org/jira/browse/CASSANDRA-6961
>
> This prevents you from decreasing your unique replica count, which is
> usually a good thing!
>
> =Rob
>

Mime
View raw message