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
Please, how do you do this?
Peter
On Fri, May 19, 2017 at 7:13 PM, Varun Gupta 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
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 wrote:
>
>
>
>> On 2017-05-19 08:13 (-0700), Haris Altaf
On 2017-05-19 08:13 (-0700), Haris Altaf 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
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 wrote:
>
> Hi All,
> I am using Cassandra 3.10 for my project and whenever my
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