*From:* Anuj Wadehra [mailto:anujw_2...@yahoo.co.in]
> *Sent:* Wednesday, April 27, 2016 10:44 PM
> *To:* user@cassandra.apache.org
> *Subject:* RE: Inconsistent Reads after Restoring Snapshot
>
>
>
> No.We are not saving them.I have never read that in DataStax documentation.
>
>
>
:
https://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configLogArchive_t.html
Sean Durity
From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in]
Sent: Wednesday, April 27, 2016 10:44 PM
To: user@cassandra.apache.org
Subject: RE: Inconsistent Reads after Restoring Snapshot
https://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configLogArchive_t.html
Sean Durity
From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in]
Sent: Wednesday, April 27, 2016 10:44 PM
To: user@cassandra.apache.org
Subject: RE: Inconsistent Reads after Restoring Snapshot
No.We are not
No.We are not saving them.I have never read that in DataStax documentation.
ThanksAnuj
Sent from Yahoo Mail on Android
On Thu, 28 Apr, 2016 at 12:45 AM,
sean_r_dur...@homedepot.com wrote:
What about the commitlogs? Are you saving those off anywhere in between the
snapshot and the crash?
What about the commitlogs? Are you saving those off anywhere in between the
snapshot and the crash?
Sean Durity
From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in]
Sent: Monday, April 25, 2016 10:26 PM
To: User
Subject: Inconsistent Reads after Restoring Snapshot
Hi,
We have 2.0.14. We use RF=
tion during autobootstrap :)
Thanks
Anuj
On Tue, 26/4/16, Romain Hardouin wrote:
Subject: Re: Inconsistent Reads after Restoring Snapshot
To: "user@cassandra.apache.org"
Date: Tuesday, 26 April, 2016, 12:47 PM
You can make a restore on t
Romain Hardouin wrote:
Subject: Re: Inconsistent Reads after Restoring Snapshot
To: "user@cassandra.apache.org"
Date: Tuesday, 26 April, 2016, 12:47 PM
You can make a restore on the new node A (don't
forget to set the token(s) in cassandra.yaml), start the
node with -Dcassandr
You can make a restore on the new node A (don't forget to set the token(s) in
cassandra.yaml), start the node with -Dcassandra.join_ring=false and then run a
repair on it. Have a look at
https://issues.apache.org/jira/browse/CASSANDRA-6961
Best,
Romain
Le Mardi 26 avril 2016 4h26, Anuj Wad