Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 29 Aug 2012 06:19:10 +1100 (NCT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1114711960.7997.1346181550273.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1105694773.13281.1330715518307.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (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:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-3991:
--------------------------------------

    Fix Version/s:     (was: 1.2.0 beta 1)
                   1.3

If the consensus is we should be fixing jsvc then I'm going to punt this to 1.3.

Are there any problems other than not respecting Xmx?  If not let's change the title to reflect the real issue.
                
> 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