[jira] [Commented] (CASSANDRA-4020) System time suddenly changed made gossip working abnormally
[
https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13229126#comment-13229126
]
MaHaiyang commented on CASSANDRA-4020:
--
{quote}
I can't repro either setting one clock forward an hour, or backward an entire
year. Which makes sense, since the gossip generation is stored in the system
table and reused.
{quote}
Sorry , I forgot a important operation in the former description . I changed
the node's system time to one hour ahead ,but several seconds later , I
changed the time to normal again.
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
[jira] [Commented] (CASSANDRA-4020) System time suddenly changed made gossip working abnormally
[ https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13229401#comment-13229401 ] Brandon Williams commented on CASSANDRA-4020: - Are you able to reproduce this consistently? If so, can you give a list of explicit steps including when to start/stop nodes that can be performed to reproduce the issue? 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
[jira] [Commented] (CASSANDRA-4020) System time suddenly changed made gossip working abnormally
[ https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (CASSANDRA-4020) System time suddenly changed made gossip working abnormally
[ https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (CASSANDRA-4020) System time suddenly changed made gossip working abnormally
[ https://issues.apache.org/jira/browse/CASSANDRA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13225245#comment-13225245 ] Brandon Williams commented on CASSANDRA-4020: - I can't repro either setting one clock forward an hour, or backward an entire year. Which makes sense, since the gossip generation is stored in the system table and reused. 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
