Thanks Jeff & Hannu, Yeah, that's my guess too, I walk around this by set -Dcassandra.commitlog.ignorereplayerrors=true.
Before upgrade, we did run `nodetool drain`, but seems the 2.1 commit log were not cleared, and still got replayed by 2.2. Thanks Dikang. On Tue, Apr 18, 2017 at 11:09 PM, Jeff Jirsa <jji...@apache.org> wrote: > > > On 2017-04-18 18:57 (-0700), Dikang Gu <dikan...@gmail.com> wrote: > > Hello there, > > > > We are upgrading one of our cluster from 2.1.14 to 2.2.5, but cassandra > had > > problems replaying the commit logs... > > > > Here is the exception, does anyone experience similar before? > > > > 2017-04-19_00:22:22.26911 ERROR 00:22:22 [main]: Exiting due to error > while > > processing commit log during initialization. > > 2017-04-19_00:22:22.26912 > > org.apache.cassandra.db.commitlog.CommitLogReplayer$ > CommitLogReplayException: > > Unexpected end of segment > > > A lot of the commitlog replay code changed from 2.1 -> 2.2 to be more > strict with "unexpected" errors on replay. Just glancing at the message but > not tracing line numbers, I'm guessing it's either > https://issues.apache.org/jira/browse/CASSANDRA-13282 (went into 2.2.10) > or https://issues.apache.org/jira/browse/CASSANDRA-11995 (PA but not yet > reviewed, would love a reviewer). > -- Dikang
