cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arya Goudarzi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3991) Investigate importance of jsvc in debian packages
Date Fri, 09 Nov 2012 04:24:15 GMT

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

Arya Goudarzi commented on CASSANDRA-3991:
------------------------------------------

+1 on this issue. I was not monitoring the inodes but JSVC definitely was eating 68Gb of memory
and using a lot of CPU. Starting cassandra without it solved the problem. It was really bad
as for a week Cassandra was being blamed but really that was not the issue. For sake of Cassandra
reputation, this deserves a higher priority.
                
> Investigate importance of jsvc in debian packages
> -------------------------------------------------
>
>                 Key: CASSANDRA-3991
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3991
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Eric Evans
>            Priority: Minor
>             Fix For: 1.3
>
>
> jsvc seems to be buggy at best.  For instance, if you set a small heap like 128M it seems
to completely ignore this and use as much memory as it wants.  I don't know what this is buying
us over launching /usr/bin/cassandra directly like the redhat scripts do, but I've seen multiple
complaints about its memory usage.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message