cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1730) Fat clients are never removed
Date Tue, 07 Dec 2010 20:31:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968948#action_12968948
] 

Hudson commented on CASSANDRA-1730:
-----------------------------------

Integrated in Cassandra #615 (See [https://hudson.apache.org/hudson/job/Cassandra/615/])
    

> 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
>            Assignee: Brandon Williams
>             Fix For: 0.6.9
>
>         Attachments: 1730.txt
>
>
> 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.


Mime
View raw message