On Mon, Jun 16, 2014 at 11:03 AM, horschi wrote:
> About running mixed versions:
> I thought running mixed versions is ok. Running repair with mixed versions
> is not though. Right?
>
Running with split major versions for longer than it takes to do a rolling
restart is not supported.
=Rob
Hi Robert,
sorry, I am using our own internal terminology :-)
The entire cluster was upgraded. All 3 nodes of that cluster are on 2.0.8
now.
About the issue:
To me it looks like there is something wrong in the Memtable class. Some
very special edge case on CFs that are updated rarely. I cant say
On Sat, Jun 14, 2014 at 1:02 PM, horschi wrote:
> this week we upgraded one of our Systems from Cassandra 1.2.16 to 2.0.8.
> All 3 nodes were upgraded. SStables are upgraded.
>
One of your *clusters* or one of your *systems*?
Running with split major versions is not supported.
=Rob
Hi again,
before people start replying here: I just reported a Jira ticket:
https://issues.apache.org/jira/browse/CASSANDRA-7401
I think Memtable.maybeUpdateLiveRatio() needs some love.
kind regards,
Christian
On Sat, Jun 14, 2014 at 10:02 PM, horschi wrote:
> Hi everyone,
>
> this week we
Hello again,
Back to this after a while...
As far as I can tell whenever DC2 is unavailable, there is one node from
DC1 that acts as a coordinator. When DC2 is available again, this one node
sends the hints to only one node at DC2, which then sends any replicas to
the other nodes in the local DC
