Return-Path: 
 <user-return-22446-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8126E9001
	for <apmail-cassandra-user-archive@www.apache.org>;
 Fri, 18 Nov 2011 16:06:23 +0000 (UTC)
Received: (qmail 44535 invoked by uid 500); 18 Nov 2011 16:06:21 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 44461 invoked by uid 500); 18 Nov 2011 16:06:21 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 44450 invoked by uid 99); 18 Nov 2011 16:06:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2011 16:06:21 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com)
 (209.85.161.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2011 16:06:14 +0000
Received: by ggeq3 with SMTP id q3so1322796gge.31
        for <user@cassandra.apache.org>; Fri, 18 Nov 2011 08:05:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.236.78.3 with SMTP id f3mr5918464yhe.120.1321632352820; Fri,
 18 Nov 2011 08:05:52 -0800 (PST)
Received: by 10.146.167.15 with HTTP; Fri, 18 Nov 2011 08:05:52 -0800 (PST)
In-Reply-To: 
 <CAAafH9SsARGGirJsGZEKrOKDj3BAOsxcN+mO_U9s9VP9xmHgHA@mail.gmail.com>
References: 
 <CAO5ofgC0afR2DkgmDyToppO-6m86Ocnp+GOLGgzmVyip0-_gcQ@mail.gmail.com>
	<CAAafH9SsARGGirJsGZEKrOKDj3BAOsxcN+mO_U9s9VP9xmHgHA@mail.gmail.com>
Date: Fri, 18 Nov 2011 11:05:52 -0500
Message-ID: 
 <CAO5ofgA39jssvCb+EF2s=hMLEdZ6-hTA=9rEmzR8JYPdp2+X5w@mail.gmail.com>
Subject: Re: BulkLoader
From: Giannis Neokleous <giannis@generalsentiment.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf300514e0e9dd2604b2048231
X-Virus-Checked: Checked by ClamAV on apache.org

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

Thanks for the info Brandon. I'll do the upgrade once 0.8.8 is released.

On Wed, Nov 16, 2011 at 2:43 PM, Brandon Williams <driftx@gmail.com> wrote:

> On Mon, Nov 14, 2011 at 2:49 PM, Giannis Neokleous
> <giannis@generalsentiment.com> wrote:
> > Hello everyone,
> >
> > We're using the bulk loader to load data every day to Cassandra. The
> > machines that use the bulkloader are diferent every day so their IP
> > addresses change. When I do "describe cluster" i see all the unreachable
> > nodes that keep piling up for the past few days. Is there a way to remove
> > those IP addresses without terminating the whole cluster at the same time
> > and restarting it?
> >
> > The unreachable nodes cause issues when we want to make schema changes to
> > all the nodes or when we want to truncate a CF.
> >
> > Any suggestions?
>
>
> It sounds like you're running into
> https://issues.apache.org/jira/browse/CASSANDRA-3351 so the first step
> would be to upgrade to a version that has it fixed.
>
> Unfortunately, this won't solve the problem, just prevent it from
> happening in the future.  To remove the old nodes, you can apply
> https://issues.apache.org/jira/browse/CASSANDRA-3337 on one node and
> call the JMX method for the unreachable endpoints.
>
> -Brandon
>

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

Thanks for the info Brandon. I&#39;ll do the upgrade once 0.8.8 is released=
.<br><br><div class=3D"gmail_quote">On Wed, Nov 16, 2011 at 2:43 PM, Brando=
n Williams <span dir=3D"ltr">&lt;<a href=3D"mailto:driftx@gmail.com">driftx=
@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 class=3D"HOEnZb"><div class=3D"h5">On =
Mon, Nov 14, 2011 at 2:49 PM, Giannis Neokleous<br>
&lt;<a href=3D"mailto:giannis@generalsentiment.com">giannis@generalsentimen=
t.com</a>&gt; wrote:<br>
&gt; Hello everyone,<br>
&gt;<br>
&gt; We&#39;re using the bulk loader to load data every day to Cassandra. T=
he<br>
&gt; machines that use the bulkloader are diferent every day so their IP<br=
>
&gt; addresses change. When I do &quot;describe cluster&quot; i see all the=
 unreachable<br>
&gt; nodes that keep piling up for the past few days. Is there a way to rem=
ove<br>
&gt; those IP addresses without terminating the whole cluster at the same t=
ime<br>
&gt; and restarting it?<br>
&gt;<br>
&gt; The unreachable nodes cause issues when we want to make schema changes=
 to<br>
&gt; all the nodes or when we want to truncate a CF.<br>
&gt;<br>
&gt; Any suggestions?<br>
<br>
<br>
</div></div>It sounds like you&#39;re running into<br>
<a href=3D"https://issues.apache.org/jira/browse/CASSANDRA-3351" target=3D"=
_blank">https://issues.apache.org/jira/browse/CASSANDRA-3351</a> so the fir=
st step<br>
would be to upgrade to a version that has it fixed.<br>
<br>
Unfortunately, this won&#39;t solve the problem, just prevent it from<br>
happening in the future. =A0To remove the old nodes, you can apply<br>
<a href=3D"https://issues.apache.org/jira/browse/CASSANDRA-3337" target=3D"=
_blank">https://issues.apache.org/jira/browse/CASSANDRA-3337</a> on one nod=
e and<br>
call the JMX method for the unreachable endpoints.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-Brandon<br>
</font></span></blockquote></div><br>

--20cf300514e0e9dd2604b2048231--