cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past
Date Wed, 09 Oct 2013 13:28:42 GMT

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

Jonathan Ellis commented on CASSANDRA-4925:
-------------------------------------------

Is this the right patch?  I still see {{Gossiper.intervalInMillis}} being used.

> Failure Detector should log or ignore sudden time change to the past
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-4925
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4925
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Minor
>             Fix For: 2.0.2
>
>         Attachments: trunk-4925.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> If a machine goes back in time all of a sudden because of a problem, Gossip will insert
a negative interArrivalTime. 
> This will decrease the mean value and can cause this machine to mark other nodes as down
and then mark them up as time passed. 
> But we should log such occurrences.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message