[ https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225195#comment-13225195 ]
Jonathan Ellis commented on CASSANDRA-4020: ------------------------------------------- My guess is that a different change caused the partition. System time in the future shouldn't cause this. (But it will cause other badness; counters in particular assume clocks are synced.) > System time suddenly changed made gossip working abnormally > ------------------------------------------------------------- > > Key: CASSANDRA-4020 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4020 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.0.6 > Reporter: MaHaiyang > > I hava four cassandra node (A,B,C,D) . > I changed node A's system time to one hour ahead, then I use nodetool's ring > command at node B , node B look node A is "down" . It's the same thing on > node C and D . But node A look itself is "UP" by ring command . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira