Return-Path: 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 467DC7D6C for ; Fri, 9 Dec 2011 14:20:48 +0000 (UTC) Received: (qmail 88655 invoked by uid 500); 9 Dec 2011 14:20:45 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 88570 invoked by uid 500); 9 Dec 2011 14:20:45 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 88562 invoked by uid 99); 9 Dec 2011 14:20:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2011 14:20:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of arodrime@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2011 14:20:39 +0000 Received: by eaad1 with SMTP id d1so246465eaa.31 for ; Fri, 09 Dec 2011 06:20:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kJQBYjiJCyEJ7Mh+TYXiP0YSd2QN/fVcfMSfQVQ1Xh0=; b=OmM/CL5hrpT8Q++L1cT1v82iZw0pDTMGWQqFaYWZrVWwKYd+hdPNqtAQPWyJIwGHxt FCpUaMScSPs3Cqt+wng54pVPnl+tUGrNqWKr9spkDScao8dMdDZjtr/lp75GvQYHgzAS dtQSAoFGw0pdkXAX0ZgUqMwNVAjTfjZwNBnug= Received: by 10.213.13.134 with SMTP id c6mr198450eba.91.1323440418097; Fri, 09 Dec 2011 06:20:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.113.200 with HTTP; Fri, 9 Dec 2011 06:19:56 -0800 (PST) In-Reply-To: References: From: Alain RODRIGUEZ Date: Fri, 9 Dec 2011 15:19:56 +0100 Message-ID: Subject: Re: BulkLoader To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0015174beaca008cb504b3a97c49 X-Virus-Checked: Checked by ClamAV on apache.org --0015174beaca008cb504b3a97c49 Content-Type: text/plain; charset=ISO-8859-1 By the way, nice comment on the patch "// do not pass go, do not collect 200 dollars, just gtfo", it looks like you have some fun while developping Cassandra @Datastax ;) Alain 2011/12/9 Alain RODRIGUEZ > Hi, I'm running a 4 nodes Cassandra cluster, and I'm facing the same > problem (node not present on nodetool ring, but unreachable on CLI describe > cluster...). I'm currently running version 1.0.2, but I have update from > 0.8.x, the problem may exist since a while, I don't really know. I can't > stop my cluster, but I don't know how to apply the patch to repair the > consequences of this bug by removing definitely this node. > > Can someone tell me the way to proceed to apply a patch and call this java > function ? > > Thank you, > > Alain > > 2011/11/18 Giannis Neokleous > >> 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 wrote: >> >>> On Mon, Nov 14, 2011 at 2:49 PM, Giannis Neokleous >>> 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 >>> >> >> > --0015174beaca008cb504b3a97c49 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable By the way, nice comment on the patch "// do not pass go, do not colle= ct 200 dollars, just gtfo", it looks like you have some fun while deve= lopping Cassandra @Datastax ;)

Alain

2011/12/9 Alain RODRIGUEZ <arodrime@gmail.com>
Hi, I'm running a 4 nodes Cassandra cluster, and I'm facing th= e same problem (node not present on nodetool ring, but unreachable on CLI d= escribe cluster...). I'm currently running version 1.0.2, but I have up= date from 0.8.x, the problem may exist since a while, I don't really kn= ow. I can't stop my cluster, but I don't know how to apply the patc= h to repair the consequences of this bug by removing definitely this node.<= /div>

Can someone tell me the way to proceed to apply a patch= and call this java function ?

Thank you,

Alain

2011/11/18 Giannis Neokleous <giannis@generalsentiment.com&= gt;
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 William= s <driftx@gmail.com> wrote:
On Mon, Nov 14, 2011 at 2:49 PM, G= iannis Neokleous
<giann= is@generalsentiment.com> wrote:
> Hello everyone,
>
> We're using the bulk loader to load data every day to Cassandra. T= he
> 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 rem= ove
> those IP addresses without terminating the whole cluster at the same t= ime
> 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 fir= st 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. =A0To remove the old nodes, you can apply
https://issues.apache.org/jira/browse/CASSANDRA-3337 on one nod= e and
call the JMX method for the unreachable endpoints.

-Brandon



--0015174beaca008cb504b3a97c49--