I will try the fixes, thanks Benjamin & Jeff.
On Thu, Sep 21, 2017 at 8:55 PM, Jeff Jirsa wrote:
> https://issues.apache.org/jira/plugins/servlet/mobile#
> issue/CASSANDRA-11995
>
>
>
> --
> Jeff Jirsa
>
>
> On Sep 19, 2017, at 4:36 PM, Dikang Gu wrote:
>
> Hello,
>
> In our production cluster,
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-11995
--
Jeff Jirsa
> On Sep 19, 2017, at 4:36 PM, Dikang Gu wrote:
>
> Hello,
>
> In our production cluster, we had multiple times that after a *unclean*
> shutdown, cassandra sever can not start due to commit log excep
It might be related to CASSANDRA-12539 (in cassandra-2.2.9).
We used to use 2 file pointers when creating commitlog segments. So if you
run out of file pointers while requesting the second file pointer you would
end up with an empty segment.
Hello,
In our production cluster, we had multiple times that after a *unclean*
shutdown, cassandra sever can not start due to commit log exceptions:
2017-09-17_06:06:32.49830 ERROR 06:06:32 [main]: Exiting due to error while
processing commit log during initialization.
2017-09-17_06:06:32.49831
o