Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of horschi@gmail.com designates
 209.85.160.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEDUwd1-zojzUHT--5RvUg9Pg=eip36Zd8wqAkYo3DfpKXGsSQ@mail.gmail.com>
References: 
 <CALY91SN45-FinfEpPo5Mo7dvfahd==9U_0p+wodjtjPy6PnDag@mail.gmail.com>
	<CAEDUwd1-zojzUHT--5RvUg9Pg=eip36Zd8wqAkYo3DfpKXGsSQ@mail.gmail.com>
Date: Mon, 16 Jun 2014 20:03:57 +0200
Message-ID: 
 <CALY91SMCq1XU_2mu0pOkkDoFiDFiNG0zOEdFYfZYfazsUOVuAg@mail.gmail.com>
Subject: Re: Cassandra 2.0.8 MemoryMeter goes crazy
From: horschi <horschi@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1cc3ee4baa304fbf7d9ab

--e89a8ff1cc3ee4baa304fbf7d9ab
Content-Type: text/plain; charset=UTF-8

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 if it is
new to 2.0 or if it already existed in 1.2.

About running mixed versions:
I thought running mixed versions is ok. Running repair with mixed versions
is not though. Right?

kind regards,
Christian


On Mon, Jun 16, 2014 at 7:50 PM, Robert Coli <rcoli@eventbrite.com> wrote:

> On Sat, Jun 14, 2014 at 1:02 PM, horschi <horschi@gmail.com> 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
>

--e89a8ff1cc3ee4baa304fbf7d9ab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Robert,<br><br>sorry, I am using our own internal =
terminology :-)<br><br>The entire cluster was upgraded. All 3 nodes of that=
 cluster are on 2.0.8 now.<br><br></div><div>About the issue:<br></div>To m=
e it looks like there is something wrong in the Memtable class. Some very s=
pecial edge case on CFs that are updated rarely. I cant say if it is new to=
 2.0 or if it already existed in 1.2.<br>
<br><div><div>About running mixed versions:<br>I thought running mixed vers=
ions is ok. Running repair with mixed versions is not though. Right?<br><br=
></div><div>kind regards,<br>Christian<br></div><div><br></div></div></div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Jun 1=
6, 2014 at 7:50 PM, Robert Coli <span dir=3D"ltr">&lt;<a href=3D"mailto:rco=
li@eventbrite.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D"">On Sat, Jun 14, 2014 at 1:02 PM,=
 horschi <span dir=3D"ltr">&lt;<a href=3D"mailto:horschi@gmail.com" target=
=3D"_blank">horschi@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div><div>this week we upgraded one of our Systems from Ca=
ssandra 1.2.16 to 2.0.8. All 3 nodes were upgraded. SStables are upgraded.<=
/div></div></div></blockquote><div><br></div></div><div>One of your *cluste=
rs* or one of your *systems*?</div>

<div><br></div><div>Running with split major versions is not supported.</di=
v><div><br></div><div>=3DRob=C2=A0</div></div></div></div>
</blockquote></div><br></div>

--e89a8ff1cc3ee4baa304fbf7d9ab--