Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <30209791.32311289503153805.JavaMail.jira@thor>
Date: Thu, 11 Nov 2010 14:19:13 -0500 (EST)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1730) Fat clients are never removed
In-Reply-To: <17469901.32231289503035055.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-1730:
----------------------------------------

    Fix Version/s: 0.6.8

> Fat clients are never removed
> -----------------------------
>
>                 Key: CASSANDRA-1730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1730
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.6.7
>            Reporter: Brandon Williams
>             Fix For: 0.6.8, 0.7.0
>
>
> After a failed bootstrap, these lines repeat infinitely:
>  INFO [Timer-0] 2010-11-11 01:58:32,708 Gossiper.java (line 406) FatClient /10.104.73.164 has been silent for 3600000ms, removing from gossip
>  INFO [GMFD:1] 2010-11-11 01:59:03,685 Gossiper.java (line 591) Node /10.104.73.164 is now part of the cluster
> Changing the IP on the node but using the same token causes a conflict, requiring either a full cluster restart or changing the token.  This is especially easy to run into in practice in a virtual environment such as ec2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.