You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Haris Altaf <m....@gmail.com> on 2017/05/19 15:13:42 UTC
Cassandra Server 3.10 unable to Start after crash - commitlog needs
to be removed
Hi All,
I am using Cassandra 3.10 for my project and whenever my local windows
system, which is my development environment, crashes then cassandra server
is unable to start. I have to delete commitlog directory after every system
crash. This is actually annoying and what's the purpose of commitlog if it
itself gets crashed. I have uploaded the entire dump of Cassandra Server
(along with logs, commitlogs, data, configs etc) at the link below. Kindly
share its solution. I believe it needs to be fixed.
Crashed Cassandra 3.10 Server Link:
https://drive.google.com/open?id=0BxE52j6oo6cEYXJvdGhBNHNQd0E
regards,
Haris
--
regards,
Haris
Re: Cassandra Server 3.10 unable to Start after crash - commitlog
needs to be removed
Posted by Cogumelos Maravilha <co...@sapo.pt>.
You can also manually delete the corrupt log file. Just check is name on
the logs.
Of course you are losing some data or not!
Cheers
On 01-06-2017 20:01, Peter Reilly wrote:
> Please, how do you do this?
>
> Peter
>
>
> On Fri, May 19, 2017 at 7:13 PM, Varun Gupta <varung@uber.com
> <ma...@uber.com>> wrote:
>
> Yes the bugs need to be fixed, but as a work around on dev
> environment, you can enable cassandra.yaml option to override any
> corrupted commit log file.
>
>
> Thanks,
> Varun
>
> > On May 19, 2017, at 11:31 AM, Jeff Jirsa <jjirsa@apache.org
> <ma...@apache.org>> wrote:
> >
> >
> >
> >> On 2017-05-19 08:13 (-0700), Haris Altaf <m.haris.ce@gmail.com
> <ma...@gmail.com>> wrote:
> >> Hi All,
> >> I am using Cassandra 3.10 for my project and whenever my local
> windows
> >> system, which is my development environment, crashes then
> cassandra server
> >> is unable to start. I have to delete commitlog directory after
> every system
> >> crash. This is actually annoying and what's the purpose of
> commitlog if it
> >> itself gets crashed. I have uploaded the entire dump of
> Cassandra Server
> >> (along with logs, commitlogs, data, configs etc) at the link
> below. Kindly
> >> share its solution. I believe it needs to be fixed.
> >>
> >
> > You need to share the exact stack trace. In cassandra 3.0+, we
> became much less tolerant of surprises in commitlog state -
> perhaps a bit too aggressive, failing to start in many cases when
> only minor things were wrong. We've recently fixed a handful of
> these, but they may not be released yet for the version you're using.
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> <ma...@cassandra.apache.org>
> > For additional commands, e-mail: user-help@cassandra.apache.org
> <ma...@cassandra.apache.org>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> <ma...@cassandra.apache.org>
> For additional commands, e-mail: user-help@cassandra.apache.org
> <ma...@cassandra.apache.org>
>
>
Re: Cassandra Server 3.10 unable to Start after crash - commitlog
needs to be removed
Posted by Peter Reilly <pe...@gmail.com>.
Please, how do you do this?
Peter
On Fri, May 19, 2017 at 7:13 PM, Varun Gupta <va...@uber.com> wrote:
> Yes the bugs need to be fixed, but as a work around on dev environment,
> you can enable cassandra.yaml option to override any corrupted commit log
> file.
>
>
> Thanks,
> Varun
>
> > On May 19, 2017, at 11:31 AM, Jeff Jirsa <jj...@apache.org> wrote:
> >
> >
> >
> >> On 2017-05-19 08:13 (-0700), Haris Altaf <m....@gmail.com> wrote:
> >> Hi All,
> >> I am using Cassandra 3.10 for my project and whenever my local windows
> >> system, which is my development environment, crashes then cassandra
> server
> >> is unable to start. I have to delete commitlog directory after every
> system
> >> crash. This is actually annoying and what's the purpose of commitlog if
> it
> >> itself gets crashed. I have uploaded the entire dump of Cassandra Server
> >> (along with logs, commitlogs, data, configs etc) at the link below.
> Kindly
> >> share its solution. I believe it needs to be fixed.
> >>
> >
> > You need to share the exact stack trace. In cassandra 3.0+, we became
> much less tolerant of surprises in commitlog state - perhaps a bit too
> aggressive, failing to start in many cases when only minor things were
> wrong. We've recently fixed a handful of these, but they may not be
> released yet for the version you're using.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: user-help@cassandra.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
>
Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
Posted by Varun Gupta <va...@uber.com>.
Yes the bugs need to be fixed, but as a work around on dev environment, you can enable cassandra.yaml option to override any corrupted commit log file.
Thanks,
Varun
> On May 19, 2017, at 11:31 AM, Jeff Jirsa <jj...@apache.org> wrote:
>
>
>
>> On 2017-05-19 08:13 (-0700), Haris Altaf <m....@gmail.com> wrote:
>> Hi All,
>> I am using Cassandra 3.10 for my project and whenever my local windows
>> system, which is my development environment, crashes then cassandra server
>> is unable to start. I have to delete commitlog directory after every system
>> crash. This is actually annoying and what's the purpose of commitlog if it
>> itself gets crashed. I have uploaded the entire dump of Cassandra Server
>> (along with logs, commitlogs, data, configs etc) at the link below. Kindly
>> share its solution. I believe it needs to be fixed.
>>
>
> You need to share the exact stack trace. In cassandra 3.0+, we became much less tolerant of surprises in commitlog state - perhaps a bit too aggressive, failing to start in many cases when only minor things were wrong. We've recently fixed a handful of these, but they may not be released yet for the version you're using.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
Posted by Jeff Jirsa <jj...@apache.org>.
On 2017-05-19 08:13 (-0700), Haris Altaf <m....@gmail.com> wrote:
> Hi All,
> I am using Cassandra 3.10 for my project and whenever my local windows
> system, which is my development environment, crashes then cassandra server
> is unable to start. I have to delete commitlog directory after every system
> crash. This is actually annoying and what's the purpose of commitlog if it
> itself gets crashed. I have uploaded the entire dump of Cassandra Server
> (along with logs, commitlogs, data, configs etc) at the link below. Kindly
> share its solution. I believe it needs to be fixed.
>
You need to share the exact stack trace. In cassandra 3.0+, we became much less tolerant of surprises in commitlog state - perhaps a bit too aggressive, failing to start in many cases when only minor things were wrong. We've recently fixed a handful of these, but they may not be released yet for the version you're using.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Cassandra Server 3.10 unable to Start after crash - commitlog needs to be removed
Posted by Hannu Kröger <hk...@gmail.com>.
I have seen this happen as well. Deleting commit logs helps to Cassandra start but of course if you are very unlucky you might lose some data.
Hannu
> On 19 May 2017, at 18.13, Haris Altaf <m....@gmail.com> wrote:
>
> Hi All,
> I am using Cassandra 3.10 for my project and whenever my local windows system, which is my development environment, crashes then cassandra server is unable to start. I have to delete commitlog directory after every system crash. This is actually annoying and what's the purpose of commitlog if it itself gets crashed. I have uploaded the entire dump of Cassandra Server (along with logs, commitlogs, data, configs etc) at the link below. Kindly share its solution. I believe it needs to be fixed.
>
> Crashed Cassandra 3.10 Server Link: https://drive.google.com/open?id=0BxE52j6oo6cEYXJvdGhBNHNQd0E
>
> regards,
> Haris
> --
> regards,
> Haris