On Tue, Nov 2, 2010 at 8:32 AM, Joe Alex wrote:
> Thanks, that clarifies why HH did not work, So have to use .7. Is
> there .6.7 ? I am using .6.6 now.
>
You can use the 0.6 branch instead, it's generally more stable than trunk.
> I did see the log entry in Node 4, adding a Hint for Node 2 and
Thanks, that clarifies why HH did not work, So have to use .7. Is
there .6.7 ? I am using .6.6 now.
I did see the log entry in Node 4, adding a Hint for Node 2 and when
Node 2 came up noticed a log entry in Node 4 that 1 row Handed Off -
so I thought it was working.
About RR - a read in Node 1 or
On Mon, Nov 1, 2010 at 8:28 PM, Joe Alex wrote:
>
> My expectation was even though Node 2 was down key written to Node 3
> or 4 should be updated in Node 2 using Hint and the subsequent reads
> to Node 1 or Node 2 itself should have got the latest value
Your expectation is correct, unfortunately
My findings - would be nice if somebody can please verify.
Critical for our eval to verify HintedHandOff, ReadRepair and
AntiEntropy works as we think it does
Node 1, 2, 3, 4
RF=3
All nodes up - Node 2 is responsible for key 1005
Write CL=ONE, Insert key 1005, value=123 in Node 1
Node 2, 3, 4 get
To keep the question simple,
If an insert or remove Key happens when the responsible Node is down
(RF=3) what is the expected behavior when the Node comes back up ?
For example Key 1005 was removed when Node 2 was down. When Node 2
came back up it started showing back ?
On Mon, Nov 1, 2010 at 2:2
I am running cassandra 0.6.6
4 nodes with RF=3
Have set the InitialTokens manually
Loaded around 4 million records
Had a question why the following is happening
Node 4 was down when a new key 1005 was added (value 123).
Node 2 which is responsible for the key added a Hint for Node 4
Node 4 was br
