On Wed, Jun 4, 2014 at 2:02 PM, ng 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 wrote:
>
>> Is there any reason you would like to take snapshot of c
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 wrote:
> On Wed, Jun 4, 2014 at 1:26 PM, ng wrote:
>
>> Is there any reason you would like to take snapshot of column family on
>> each node whe
On Wed, Jun 4, 2014 at 1:26 PM, ng 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 non
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 snaps
