yes, you where correct. resetting the flag and bouncing cassandra fixed
it. thx
On 7/2/2012 8:59 AM, Joost van de Wijgerd wrote:
Could be related to the leap second bug..
try this:
Bug: https://lkml.org/lkml/2012/6/30/122
Simple fix to reset the leap second flag: date; date `date
+"%m%d%H%M%C%y.%S"`; date;
mvg
Joost
On Mon, Jul 2, 2012 at 5:43 PM, Deno Vichas <d...@syncopated.net> wrote:
all,
my 4 node cluster seems pretty screwed up after the AWS outage. we found
all our machines with their cpu stuck at 100%. so i went to restart each
cassandra node one by one. i did node with token id 0 first. i came back
but doesn't look like it doing anything. once i thought it was up i went
and restarted the next. this one got stuck on the AMI init startup. i
cancelled it, rebooted againg and now it't suck with "[INFO]
07/02/12-15:42:29 Received 0 of 1 responses from: "
suggestions on how to fix this?
thanks,
deno
