cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herman Meerlo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4066) Cassandra cluster stops responding on time change (scheduling not using monotonic time?)
Date Sun, 01 Jul 2012 11:13:53 GMT


Herman Meerlo commented on CASSANDRA-4066:

Same here, certainly no kernel panics but nodes in the cluster just started marking each other
as being dead:

 INFO [GossipTasks:1] 2012-07-01 02:00:55,110 (line 818) InetAddress /
is now dead.
 INFO [GossipStage:1] 2012-07-01 02:02:41,853 (line 804) InetAddress /
is now UP
> Cassandra cluster stops responding on time change (scheduling not using monotonic time?)

> -----------------------------------------------------------------------------------------
>                 Key: CASSANDRA-4066
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Linux; CentOS6 2.6.32-220.4.2.el6.x86_64
>            Reporter: David Daeschler
>            Assignee: Brandon Williams
>            Priority: Minor
>              Labels: gossip
>             Fix For: 1.1.1
> 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
> 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:!default.jspa
For more information on JIRA, see:


View raw message