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
Thanks Romain !! So just to clarify, you are suggesting following steps:
10 AM Daily Snapshot taken of node A and moved to backup location
11 AM A record is inserted such that node A and B insert the record but there
is a mutation drop on node C.
1 PM Node A crashes
1 PM Follow following steps
Yes the "Node restart method" with -Dcassandra.join_ring=false. Note that they
advise to make a repair anyway. But thanks to join_ring=false the node will
hibernate and not serve stale data.Tell me if I'm wrong you assume that server
A is still OK, therefore system keyspace still exist? If not (
Hello,
Maybe you should call « nodetool drain » just before stoping the node.
As it flush the memtables, the commitlog will be empty and so easier to
move.
https://docs.datastax.com/en/cassandra/2.0/cassandra/tools/toolsDrain.html
--
Jérôme Mainaud
jer...@mainaud.com
2016-04-26 8:44 GMT+02:00
Did you use a backup of the keyspace system?
If not, you might do removenode of that node and re added to the cluster to
re generate new tokens.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Apr 26, 2016 at 12:06 AM, ssiv...@gmail.com
wrote:
> Hi A
No, I didn't. I just want to understand how C* handle such case and what
is a predictable behavior.
On 04/26/2016 02:51 PM, Jean Carlo wrote:
Did you use a backup of the keyspace system?
If not, you might do removenode of that node and re added to the
cluster to re generate new tokens.
Sal
Well that may explain why you do have an unbalanced distribution of data.
It is not cassandra normal behaivor. If you lose your disk, and you don't
have a backup of your data (at least system because it is not replicated),
this is what I think should be the normal procedure to recover your node.
-
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.14.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.6.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
Just following up... Oleg, have you gotten a satisfactory level of feedback
from the community on the security assessment issues?
And if there is any sort of final assessment that can be publicly accessed,
that would be great.
-- Jack Krupansky
On Thu, Feb 11, 2016 at 3:29 PM, oleg yusim wrote:
10 matches
Mail list logo
