In this case, yes. I was asking for the cases where commit log corruption was
reported.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-Exception-when-starting-tp6383464p6387101.html
Sent from the cassandra-u...@incubator.apache.org mailing
duction :) It's good to
> know it's fixed.
>
> Another question, when this happens are we able to restore data from
> replica
> nodes?
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-Ex
this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-Exception-when-starting-tp6383464p6386925.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
In my case I started cassandra after sometime with the newer version of it.
I think this occurred because there were some files remained belongs to the
previous version of cassandra and overwritten with the new one.
This is just my thought.
Thanks
Eranda
onfig error, bug etc. It will be good to identify why these
> things happen so that it can be fixed before it happens in PROD :(
>
> --
> View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-Exception-when-starting-tp6383464p6386
:(
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Re-Exception-when-starting-tp6383464p6386809.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Thanks Brandon,
All data in /var/lib/cassandra was corrupted and after removing them it
started normally.
On Thu, May 19, 2011 at 1:51 PM, Eranda Sooriyabandara
<0704...@gmail.com> wrote:
> Hi devs,
> I tried to start the Apache Cassandra and got an exception. This is what log
> says,
>
> INFO 00:18:12,226 Logging initialized
> INFO 00:18:12,278 Heap size: 1029701632/1029701632
> INFO 00:18:12,281 JN
