[jira] [Comment Edited] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

["sankalp kohli (JIRA)" <ji...@apache.org>]

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

sankalp kohli edited comment on CASSANDRA-4925 at 10/8/13 5:23 PM:
-------------------------------------------------------------------

Fixed the Gossip interval and updated the patch
[~brandon.williams]  If I am not wrong, we are now using nano which is a counter and difference of a counter(higher - lower) will always be positive even with overflow.


was (Author: kohlisankalp):
With the Gossiper milli fix

> 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)