huge great thanks it is the leap second problem!
finally I can go to bed
On Mon, Jul 2, 2012 at 12:11 AM, David Daeschler
wrote:
> This looks like the problem a bunch of us were having yesterday that
> isn't cleared without a reboot or a date command. It seems to be
> related to the lea
This looks like the problem a bunch of us were having yesterday that
isn't cleared without a reboot or a date command. It seems to be
related to the leap second that was added between the 30th June and
the 1st of July.
See the mailing list thread with subject "High CPU usage as of 8pm eastern time
adjust the timezone of java by -Duser.timezone and the timezone of
cassandra is the same with system(Debian 6.0).
after restart cassandra I found the following error message in the log file
of node B. after about 2 minutes later, node C stop responding
the error log of node B:
Thrift tran
I have a three node cluster running 1.0.2, today there's a very strange
problem that suddenly two of cassandra node(let's say B and C) was costing
a lot of cpu, turned out for some reason the "java" binary just dont
run I am using OpenJDK1.6.0_18, so I switched to "sun jdk", which works
okay.
