[
https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229831#comment-13229831
]
MaHaiyang commented on CASSANDRA-4020:
--------------------------------------
Yes.
step1: all nodes(A,B,C,D) are "UP" and "Normal" ;
step2: change A's system time one hour forward;
step3: 5 seconds later ,change A's system time one hour backward.
step4: use nodetool's ring command to check node A's status. It will turns out
that node A look itself is "UP" ,but other nodes look node A is "down" .
step5: this symptom would be removed by restart node A .
> 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 and change the time to
> normal after serval seconds.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