You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Christopher Wirt <ch...@struq.com> on 2013/09/11 11:59:55 UTC
Cassandra 2 Upgrade
Hello,
I'm keen on moving to 2.0. The new thrift server implementation and other
performance improvements are getting me excited.
I'm currently running 1.2.8 in 3 DC's with 3-3-9 nodes 64GB RAM, 3x200GB
SSDs, thrift, LCS, Snappy, Vnodes,
Is anyone using 2.0 in production yet? Had any issues? I haven't seen
anything popup here or on JIRA, so either there are none/few, or nobody is
using it yet.
How important is it to move to 1.2.9 before 2.0? To me it looks like 1.2.8
to 2.0 will be fine.
Am I ok running a mixed cluster for 24 hours? E.g. I switched just one DC
for 24 hours as a test.
Size-tiered compaction on L0 compaction strategy will be default now for
LCS?
Thanks
Chris
Re: Cassandra 2 Upgrade
Posted by "Langston, Jim" <Ji...@compuware.com>.
Hi Rob,
Did you every create this blog post ?
Jim
From: Robert Coli <rc...@eventbrite.com>>
Reply-To: <us...@cassandra.apache.org>>
Date: Wed, 11 Sep 2013 10:38:58 -0700
To: "user@cassandra.apache.org<ma...@cassandra.apache.org>" <us...@cassandra.apache.org>>
Subject: Re: Cassandra 2 Upgrade
On Wed, Sep 11, 2013 at 2:59 AM, Christopher Wirt <ch...@struq.com>> wrote:
I’m keen on moving to 2.0. The new thrift server implementation and other performance improvements are getting me excited.
I’m currently running 1.2.8 in 3 DC’s with 3-3-9 nodes 64GB RAM, 3x200GB SSDs, thrift, LCS, Snappy, Vnodes,
History indicates that you should not run a Cassandra version x.y.z where z < 5 in production. Unless your bosses have tasked you with finding potentially serious bugs in your database software in production.
Is anyone using 2.0 in production yet? Had any issues? I haven’t seen anything popup here or on JIRA, so either there are none/few, or nobody is using it yet.
I'm sure some brave/foolish souls must be...
How important is it to move to 1.2.9 before 2.0? To me it looks like 1.2.8 to 2.0 will be fine.
All upgrades to 2.0 must pass through 1.2.9. I'll be doing a blog post on the upgrade path from 1.2.x to 2.0.x soon, but for now you can refer to this thread :
http://mail-archives.apache.org/mod_mbox/cassandra-user/201308.mbox/%3CCALeHUF-wjuuOe_7ytQKxdd+bvxHukLUccJnnEc4kPbMoxs8vMQ@mail.gmail.com%3E
=Rob
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it
Re: Cassandra 2 Upgrade
Posted by Robert Coli <rc...@eventbrite.com>.
On Wed, Sep 11, 2013 at 2:59 AM, Christopher Wirt <ch...@struq.com>wrote:
> I’m keen on moving to 2.0. The new thrift server implementation and other
> performance improvements are getting me excited.
>
> **
>
> I’m currently running 1.2.8 in 3 DC’s with 3-3-9 nodes 64GB RAM, 3x200GB
> SSDs, thrift, LCS, Snappy, Vnodes,
>
History indicates that you should not run a Cassandra version x.y.z where z
< 5 in production. Unless your bosses have tasked you with finding
potentially serious bugs in your database software in production.
> **
>
> Is anyone using 2.0 in production yet? Had any issues? I haven’t seen
> anything popup here or on JIRA, so either there are none/few, or nobody is
> using it yet.
>
I'm sure some brave/foolish souls must be...
> **
>
> How important is it to move to 1.2.9 before 2.0? To me it looks like 1.2.8
> to 2.0 will be fine.
>
All upgrades to 2.0 must pass through 1.2.9. I'll be doing a blog post on
the upgrade path from 1.2.x to 2.0.x soon, but for now you can refer to
this thread :
http://mail-archives.apache.org/mod_mbox/cassandra-user/201308.mbox/%3CCALeHUF-wjuuOe_7ytQKxdd+bvxHukLUccJnnEc4kPbMoxs8vMQ@mail.gmail.com%3E
=Rob
Re: Cassandra 2 Upgrade
Posted by Robert Coli <rc...@eventbrite.com>.
On Wed, Sep 11, 2013 at 2:59 AM, Christopher Wirt <ch...@struq.com>wrote:
> Am I ok running a mixed cluster for 24 hours? E.g. I switched just one DC
> for 24 hours as a test.
>
(missed this line)
This is unsupported, generally. It may or may not work. I wouldn't do it.
=Rob