We also experienced same, i.e. high cpu on Cassandra 1.1.4 node running in
AWS. Restarting the vm worked.
On Wed, Jul 1, 2015 at 4:58 AM, Jason Wee peich...@gmail.com wrote:
same here too, on branch 1.1 and have not seen any high cpu usage.
On Wed, Jul 1, 2015 at 2:52 PM, John Wong
same here too, on branch 1.1 and have not seen any high cpu usage.
On Wed, Jul 1, 2015 at 2:52 PM, John Wong gokoproj...@gmail.com wrote:
Which version are you running and what's your kernel version? We are still
running on 1.2 branch but we have not seen any high cpu usage yet...
On Tue,
I think it is more a kernel / java version issue than a Cassandra version
related issue.
From Datastax:
Leap Second on June 30, 2015
Required Actions:
Ensure that you are running on kernel version 3.4 or higher and using JDK
version 7u60 or higher. This should protect you from the livelock
Here is the full Datastax article:
http://www.datastax.com/dev/blog/preparing-for-the-leap-second
We had issues with C* and MySQL last time around (2012) but no issues this
time thanks to upgraded systems.
On 1 July 2015 at 14:39, Alain RODRIGUEZ arodr...@gmail.com wrote:
I think it is more a
reboot of the machine worked
From: nair...@outlook.com
To: user@cassandra.apache.org
Subject: Cassandra leap second
Date: Wed, 1 Jul 2015 02:54:53 +
Is it ok to run this
https://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-and-the-fix/
Seeing high cpu
