Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1272422258.1239384374856.JavaMail.jira@brutus>
Date: Fri, 10 Apr 2009 10:26:14 -0700 (PDT)
From: "Avinash Lakshman (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-14) The initial arrive time should not
 be set to zero
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Avinash Lakshman commented on CASSANDRA-14:
-------------------------------------------

Hmm. That is weird. Because I have small, 5 node test cluster, and it definitely doesn't take minutes. Maybe the recovery is taking time. Nodes do not join the cluster untill recovery is complete.

> The initial arrive time should not be set to zero
> -------------------------------------------------
>
>                 Key: CASSANDRA-14
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: zhu han
>            Assignee: Avinash Lakshman
>             Fix For: 0.3
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> In line 253 of src.org.apache.cassandra.gms .FailureDetector, the initial arrive time should not be zero. Otherwise, the failure detector would report the new joining node as dead because the phi is positive infinity when the mean of arrive time is zero. 
> A proper value should be set as the initial value. I use half of the gossip period as the initial value,  whose default configuration is 1000ms. 

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