I too have noticed that after doing “nodetool flush” (or “nodetool drain”), the
commit logs are still there. I think they’re NEW (empty) commit logs, but I may
be wrong. Anyone know?
Don
From: Gaurav Sehgal [mailto:gsehg...@gmail.com]
Sent: Monday, May 12, 2014 12:31 PM
To: user@cassandra.apach
On Tue, May 13, 2014 at 5:11 PM, Donald Smith <
donald.sm...@audiencescience.com> wrote:
> I too have noticed that after doing “nodetool flush” (or “nodetool
> drain”), the commit logs are still there. I think they’re NEW (empty)
> commit logs, but I may be wrong. Anyone know?
>
Assuming they ar
Hey Gaurav,
You should consider moving to 2.0.7 which fixes a bunch of these schema
disagreement problems. You could also play around with nodetool
resetlocalschema on the nodes that are behind, but be careful with that
one. I'd go with 2.0.7 first for sure.
Thanks,
Vince.
On Mon, May 12, 2
Hi Gaurav, a schema versioning bug was fixed in 2.0.7.
Best wishes, Duncan.
On 12/05/14 21:31, Gaurav Sehgal wrote:
We have recently started seeing a lot of Schema Disagreement errors. We are
using Cassandra 2.0.6 with Oracle Java 1.7. I went through the Cassandra FAQ and
followed the below ste
Upgrade to 2.0.7 fixed this for me.
You can also try 'nodetool resetlocalschema' on disagreeing nodes. This
worked temporarily for me in 2.0.6.
ml
On Mon, May 12, 2014 at 3:31 PM, Gaurav Sehgal wrote:
> We have recently started seeing a lot of Schema Disagreement errors. We
> are using Cassan
