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 <[email protected]
> <mailto:[email protected]>> 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 <[email protected]
>     <mailto:[email protected]>> wrote:
>     >
>     >
>     >
>     >> On 2017-05-19 08:13 (-0700), Haris Altaf <[email protected]
>     <mailto:[email protected]>> 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: [email protected]
>     <mailto:[email protected]>
>     > For additional commands, e-mail: [email protected]
>     <mailto:[email protected]>
>     >
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: [email protected]
>     <mailto:[email protected]>
>     For additional commands, e-mail: [email protected]
>     <mailto:[email protected]>
>
>

Reply via email to