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 rcoli@eventbrite.com designates
 209.85.216.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1378164094.858494080@f158.i.mail.ru>
References: <1378164094.858494080@f158.i.mail.ru>
Date: Tue, 3 Sep 2013 11:11:16 -0700
Message-ID: 
 <CAEDUwd3fVtzeVgSiuDWm9GN3Sq-_mmV6EToFT7PKJ5nQJDjWWw@mail.gmail.com>
Subject: Re: Cassandra cluster migration in Amazon EC2
From: Robert Coli <rcoli@eventbrite.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>,
 Renat Gilfanov <grennat@mail.ru>
Content-Type: multipart/alternative; boundary=089e015374687376fb04e57e9dc2

--089e015374687376fb04e57e9dc2
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 2, 2013 at 4:21 PM, Renat Gilfanov <grennat@mail.ru> wrote:

> - Group 3 of storages into raid0 array, move data directory to the raid0,
> and commit log - to the 4th left storage.
>  - As far as I understand, separation of commit log and data directory
> should make performance better - but what about separation the OS from
> those two  - is it worth doing?
>

Nope. Best practice for amazon is ephemeral disks, and RAID0 for data +
commit log.


>  - What are the steps to perform such migration? Will it be possible to
> perform it without downtime, restarting node by node with new configuration
> applied?
>  I'm especially worried about IP changes, when we'll uprade the instance
> type. What's the recomended way to handle those IP changes?
>

Just set auto_bootstrap:false in cassandra.yaml to change the IP address of
a node to which you have copied all the data its token had before its IP
address changed and therefore does not need to be bootstrapped.

=Rob

--089e015374687376fb04e57e9dc2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Sep 2, 2013 at 4:21 PM, Renat Gilfanov <span dir=
=3D"ltr">&lt;<a href=3D"mailto:grennat@mail.ru" target=3D"_blank">grennat@m=
ail.ru</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<div>- Group 3 of storages into raid0 array, move data directory to the rai=
d0, and commit log - to the 4th left storage.<br></div>=A0- As far as I und=
erstand, separation of commit log and data directory should make performanc=
e better - but what about separation the OS from those two=A0 - is it worth=
 doing?<br>
</blockquote><div><br></div><div>Nope. Best practice for amazon is ephemera=
l disks, and RAID0 for data + commit log.</div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px=
;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1e=
x">
<div>=A0- What are the steps to perform such migration? Will it be possible=
 to perform it without downtime, restarting node by node with new configura=
tion applied?<br>=A0I&#39;m especially worried about IP changes, when we=
9;ll uprade the instance type. What&#39;s the recomended way to handle thos=
e IP changes?<br>
</div></blockquote><div><br></div><div>Just set auto_bootstrap:false in cas=
sandra.yaml to change the IP address of a node to which you have copied all=
 the data its token had before its IP address changed and therefore does no=
t need to be bootstrapped.</div>
<div><br></div><div>=3DRob</div></div></div></div>

--089e015374687376fb04e57e9dc2--