Hello, it is not related to cassandra/ddos. it is kernel problems due to leap second. See http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second
On Sun, Jul 1, 2012 at 1:05 PM, ruslan usifov <ruslan.usi...@gmail.com> wrote: > Hello > > We was under ddos attack, and as result we got high ksoftirqd activity > - as result cassandra begin answer very slow. But when ddos was gone > high ksoftirqd activity still exists, and dissaper when i stop > cassandra daemon, and repeat again when i start cassadra daemon, the > fully resolution of problem is full reboot of server. What this can be > (why ksoftirqd begin work very intensive when cassandra runing - we > disable all working traffic to cluster but this doesn't help so this > is can't be due heavy load )? And how to solve this? > > PS: > OS ubuntu 10.0.4 (2.6.32.41) > cassandra 1.0.10 > java 1.6.32 (from oracle)
