Cassandra cluster stops responding on time change (scheduling not using
monotonic time?)
-----------------------------------------------------------------------------------------
Key: CASSANDRA-4066
URL: https://issues.apache.org/jira/browse/CASSANDRA-4066
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.0.6
Environment: Linux; CentOS6 2.6.32-220.4.2.el6.x86_64
Reporter: David Daeschler
The server installation I set up did not have ntpd installed in the base
installation. When I noticed that the clocks were skewing I installed ntp and
set the date on all the servers in the cluster. A short time later, I started
getting UnavailableExceptions on the clients.
Also, one sever seemed to be unaffected by the time change. That server
happened to have it's time pushed forward, not backwards like the other 3 in
the cluster. This leads me to believe something is running on a timer/schedule
that is not monotonic.
I'm posting this as a bug, but I suppose it might just be part of the
communication protocols etc for the cluster and part of the design. But I think
the devs should be aware of what I saw.
Otherwise, thank you for a fantastic product. Even after restarting 75% of the
cluster things seem to have recovered nicely.
--
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
