RE: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

[mailto:arodr...@gmail.com] Sent: Wednesday, May 11, 2016 10:01 PM To: u...@cassandra.apache.org Cc: dev@cassandra.apache.org Subject: Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot Hi Michaels :-), My guess is this ticket will be closed with a "Won't Fix"

Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

> From: Michael Kjellman [mailto:mkjell...@internalcircle.com] > Sent: Monday, May 09, 2016 11:57 AM > To: dev@cassandra.apache.org > Cc: u...@cassandra.apache.org > Subject: Re: Cassandra 2.0.x OOM during startsup - schema version > inconsistency after reboot > > I'd re

RE: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

...@internalcircle.com] Sent: Monday, May 09, 2016 11:57 AM To: dev@cassandra.apache.org Cc: u...@cassandra.apache.org Subject: Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot I'd recommend you create a JIRA! That way you can get some traction on the issue. Obviously

Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

I'd recommend you create a JIRA! That way you can get some traction on the issue. Obviously an OOM is never correct, even if your process is wrong in some way! Best, kjellman Sent from my iPhone > On May 8, 2016, at 8:48 PM, Michael Fong > wrote: > > Hi,

RE: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

Hi, all, Haven't heard any responses so far, and this isue has troubled us for quite some time. Here is another update: We have noticed several times that The schema version may change after migration and reboot: Here is the scenario: 1. Two node cluster (1 & 2). 2. There are