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 yulinyen@gmail.com designates
 74.125.82.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACHzRHbs=Ws-JCzMAS0myO0xuZ4YbG25QMAALfS+UbzznQ0X+w@mail.gmail.com>
References: 
 <CAAaMp50SW3kd56P-TsRj8j7h69zrwy6fHgh+NMMi3j8S8dNZ-A@mail.gmail.com>
	<E5BCB10F-B5B4-4B2B-B449-54C6B0FC0DBD@thelastpickle.com>
	<CACHzRHbs=Ws-JCzMAS0myO0xuZ4YbG25QMAALfS+UbzznQ0X+w@mail.gmail.com>
Date: Wed, 23 May 2012 09:12:11 +0800
Message-ID: 
 <CAAaMp5362WTeEaVmn7KO-_rZ9yvssDeCozXu6ggjtRE4LhQKAA@mail.gmail.com>
Subject: Re: exception when cleaning up...
From: Boris Yen <yulinyen@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=f46d0438904923010b04c0a9d3b0

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

Hi Aaron, Rob,

Thanks for the information, I will try it.

Regards,
Boris

On Tue, May 22, 2012 at 11:47 PM, Rob Coli <rcoli@palominodb.com> wrote:

> On Tue, May 22, 2012 at 3:00 AM, aaron morton <aaron@thelastpickle.com>
> wrote:
> > 1) Isolating the node from the cluster to stop write activity. You can
> > either start the node with the -Dcassandra.join_ring=false  JVM option or
> > use nodetool disablethrift and disablegossip to stop writes. Note that
> this
> > will not stop existing Hinted Handoff sessions which target the node.
>
> As a result of the last caveat here, I recommend either restarting the
> node with the join_ring as false or using iptables to firewall off
> ports 7000 and 9160. If you want to be sure that you have stopped
> write activity right now, nuking these ports from orbit is the only
> way to be sure. disablethrift/disablegossip as currently implemented
> are not sufficient for this goal.
>
> https://issues.apache.org/jira/browse/CASSANDRA-4162
>
> =Rob
>
> --
> =Robert Coli
> AIM&GTALK - rcoli@palominodb.com
> YAHOO - rcoli.palominob
> SKYPE - rcoli_palominodb
>

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

Hi Aaron, Rob,<div><br></div><div>Thanks for the information, I will try it=
.</div><div><br></div><div>Regards,</div><div>Boris<br><br><div class=3D"gm=
ail_quote">On Tue, May 22, 2012 at 11:47 PM, Rob Coli <span dir=3D"ltr">&lt=
;<a href=3D"mailto:rcoli@palominodb.com" target=3D"_blank">rcoli@palominodb=
.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 class=3D"im">On Tue, May 22, 2012 at 3:=
00 AM, aaron morton &lt;<a href=3D"mailto:aaron@thelastpickle.com">aaron@th=
elastpickle.com</a>&gt; wrote:<br>

&gt; 1) Isolating the node from the cluster to stop write activity. You can=
<br>
&gt; either start the node with the -Dcassandra.join_ring=3Dfalse =A0JVM op=
tion or<br>
&gt; use nodetool disablethrift and disablegossip to stop writes. Note that=
 this<br>
&gt; will not stop existing Hinted Handoff sessions which target the node.<=
br>
<br>
</div>As a result of the last caveat here, I recommend either restarting th=
e<br>
node with the join_ring as false or using iptables to firewall off<br>
ports 7000 and 9160. If you want to be sure that you have stopped<br>
write activity right now, nuking these ports from orbit is the only<br>
way to be sure. disablethrift/disablegossip as currently implemented<br>
are not sufficient for this goal.<br>
<br>
<a href=3D"https://issues.apache.org/jira/browse/CASSANDRA-4162" target=3D"=
_blank">https://issues.apache.org/jira/browse/CASSANDRA-4162</a><br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=3DRob<br>
<br>
--<br>
=3DRobert Coli<br>
AIM&amp;GTALK - <a href=3D"mailto:rcoli@palominodb.com">rcoli@palominodb.co=
m</a><br>
YAHOO - rcoli.palominob<br>
SKYPE - rcoli_palominodb<br>
</font></span></blockquote></div><br></div>

--f46d0438904923010b04c0a9d3b0--