Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 8 Jun 2012 23:52:23 +0000 (UTC)
From: "Viktor Kuzmin (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1216375373.55050.1339199543461.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1105694773.13281.1330715518307.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3991) Investigate importance of jsvc
 in debian packages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Viktor Kuzmin commented on CASSANDRA-3991:
------------------------------------------

Os: Debian Squeeze (minimal setup, latest packages at the moment of post)

After upgrading from 1.1.0 to 1.1.1 I've faced the problem with error: "Too many open files"
After investigation it appears that it was jsvc who spawns lot's of unix sockets FD's for communication between forked processes.

There is no more such problem after moving to start-stop-daemon.
                
> 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: Brandon Williams
>            Priority: Minor
>             Fix For: 1.2
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira