cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9578) CPU hogging by cassandra while starting.
Date Wed, 08 Jul 2015 16:57:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618924#comment-14618924
] 

Michael Shuler commented on CASSANDRA-9578:
-------------------------------------------

What do your logs tell you when you see the load increase? Repairs, compactions, etc.? Dig
through various nodetool reporting options and see if you can find details that might help
you see what Cassandra is doing. When Cassandra node is overloaded, DN status can occur and
is a symptom of overload - why is the node overloaded?

> CPU hogging by cassandra while starting.
> ----------------------------------------
>
>                 Key: CASSANDRA-9578
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9578
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: pankaj mishra
>
> The problem we experience is that just after starting cassandra, the cpu utilization
by java program (cassandra service) increases insanely (100-300%) and cassandra server startup
process gets delayed forever.  It does not happen every time we start. Many a times it starts
just fine.
> We also observed that while cluster is running fine with every node is in UN mode, after
one or two days (time period is not fixed) few nodes goes into DN mode in nodetool status
on their own, even though we are not reading any data or even writing any data.
> We just wanted to know that is there any corner case bug in cassandra that might be the
reason for this kind of behavior?
> The version of cassandra server along with all environment information is given below.
> Cassandra server version  2.0.14
> JDK version 
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> unama -a
> Linux  2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr 22 06:48:29 UTC 2015 x86_64 x86_64 x86_64
GNU/Linux
> blockdev --getra /dev/sdb1 (cassandra data directory)
> 128
>  blockdev --getra /dev/sda2  (cassandra commitlog directory)
> 128
> lbs_release -a
> LSB Version:	:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
> Distributor ID:	CentOS
> Description:	CentOS release 6.6 (Final)
> Release:	6.6
> Codename:	Final
>   
> We are using following version of cassandra on vm with following version of os.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message