You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by ng <pi...@gmail.com> on 2014/06/04 22:26:49 UTC
Snapshot the data with 3 node and replicationfactor=3
Is there any reason you would like to take snapshot of column family on
each node when cluster consists of 3 nodes with keyspace on replication
factor =3?
I am thinking of taking snapshot of CF on only one node.
For restore, I will follow below
1. drop and recreate the CF on node1
2. copy snapshotted files to node 1 data directory of CF
3. perform nodetool refresh on node 1
Any suggestions/advise?
ng
Re: Snapshot the data with 3 node and replicationfactor=3
Posted by Robert Coli <rc...@eventbrite.com>.
On Wed, Jun 4, 2014 at 2:02 PM, ng <pi...@gmail.com> wrote:
> I am not worried about eventually consistent data. I just wanted to get
> rough data in close proximate.
>
Ok, but your original question was....
On Wed, Jun 4, 2014 at 1:26 PM, ng <pi...@gmail.com> wrote:
>
>> Is there any reason you would like to take snapshot of column family on
>>> each node when cluster consists of 3 nodes with keyspace on replication
>>> factor =3?
>>>
>>
... to which the answer is "yes."
=Rob
Re: Snapshot the data with 3 node and replicationfactor=3
Posted by ng <pi...@gmail.com>.
I am not worried about eventually consistent data. I just wanted to get
rough data in close proximate.
ng
On Wed, Jun 4, 2014 at 2:49 PM, Robert Coli <rc...@eventbrite.com> wrote:
> On Wed, Jun 4, 2014 at 1:26 PM, ng <pi...@gmail.com> wrote:
>
>> Is there any reason you would like to take snapshot of column family on
>> each node when cluster consists of 3 nodes with keyspace on replication
>> factor =3?
>>
>
> Unless all read/write occurs with CL.ALL (which is an availability
> problem), there is a nonzero chance of any given write not being on any
> given node at any given time.
>
> =Rob
>
>
Re: Snapshot the data with 3 node and replicationfactor=3
Posted by Robert Coli <rc...@eventbrite.com>.
On Wed, Jun 4, 2014 at 1:26 PM, ng <pi...@gmail.com> wrote:
> Is there any reason you would like to take snapshot of column family on
> each node when cluster consists of 3 nodes with keyspace on replication
> factor =3?
>
Unless all read/write occurs with CL.ALL (which is an availability
problem), there is a nonzero chance of any given write not being on any
given node at any given time.
=Rob