On Wed, Jun 19, 2013 at 4:35 PM, Wei Zhu wrote:
> I was not aware of that. So we can avoid repair if there is no hardware
> failure...I found a blog:
>
> http://www.datastax.com/dev/blog/modern-hinted-handoff
Well... yes but no.
First, I do not believe that hardware failure is required, I believ
ould I be filing
a bug report, and if so what diagnostics are likely to be useful?
Thanks,
James Lee
-Original Message-
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: 19 June 2013 20:59
To: user@cassandra.apache.org; Wei Zhu
Subject: Re: Data not fully replicated with 2
s are likely to be useful?
Thanks,
James Lee
-Original Message-
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: 19 June 2013 20:59
To: user@cassandra.apache.org; Wei Zhu
Subject: Re: Data not fully replicated with 2 nodes and replication factor 2
On Wed, Jun 19, 2013 at 11:43 AM,
ent: Wednesday, June 19, 2013 12:58:45 PM
Subject: Re: Data not fully replicated with 2 nodes and replication factor 2
On Wed, Jun 19, 2013 at 11:43 AM, Wei Zhu wrote:
> I think hints are only stored when the other node is down, not on the
> dropped mutations. (Correct me if I am wrong, ac
On Wed, Jun 19, 2013 at 11:43 AM, Wei Zhu wrote:
> I think hints are only stored when the other node is down, not on the
> dropped mutations. (Correct me if I am wrong, actually it's not a bad idea
> to store hints for dropped mutations and replay them later?)
This used to be the way it worked pr
u see that many dropped mutations.
-Wei
- Original Message -
From: "James Lee"
To: user@cassandra.apache.org
Sent: Wednesday, June 19, 2013 2:22:39 AM
Subject: RE: Data not fully replicated with 2 nodes and replication factor 2
The test tool I am using catches any except
nt: 18 June 2013 19:45
To: user@cassandra.apache.org
Subject: Re: Data not fully replicated with 2 nodes and replication factor 2
On Tue, Jun 18, 2013 at 11:36 AM, Wei Zhu wrote:
> Cassandra doesn't do async replication like HBase does.You can run
> nodetool repair to insure the consist
On Tue, Jun 18, 2013 at 11:36 AM, Wei Zhu wrote:
> Cassandra doesn't do async replication like HBase does.You can run nodetool
> repair to insure the consistency.
While this answer is true, it is somewhat non-responsive to the OP.
If the OP didn't see timeout exception, the theoretical worst cas
Cassandra doesn't do async replication like HBase does.You can run nodetool
repair to insure the consistency.
Or you can increase your Read or Write consistency. As long as R + W > RF, you
have strong consistency. In your case, you can use CL.TWO for either read and
write.
-Wei
- Origi
