Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 14 Oct 2015 18:26:06 +0000 (UTC)
From: "Paulo Motta (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12901053.1443456530000.39821.1444847166196@Atlassian.JIRA>
In-Reply-To: <JIRA.12901053.1443456530000@Atlassian.JIRA>
References: <JIRA.12901053.1443456530000@Atlassian.JIRA>
 <JIRA.12901053.1443456530912@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-10403) Consider reverting to CMS
 GC on 3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paulo Motta edited comment on CASSANDRA-10403 at 10/14/15 6:25 PM:
-------------------------------------------------------------------

For some reason, {{cassandra-env.sh}} is called before loading {{debian/cassandra.in.sh}} on {{debian/init}}. Since the init script already defines {{CASSANDRA_HOME}}, I assume it's safe to also define {{CASSANDRA_CONF}} in a similar way. Another option would be to load {{cassandra.in.sh}} before sourcing {{cassandra-env.sh}}, but I don't think this should be necessary because we're dealing with pre-defined package directories (eg. /usr/share/cassandra and /etc/cassandra), so it should be safe to define them in a static way. It's always better to confirm though.


was (Author: pauloricardomg):
For some reason, {{cassandra-env.sh}} is called before loading {{debian/cassandra.in.sh}} on {{debian/init}}. Since the init script already defines {{CASSANDRA_HOME}}, I assume it's safe to also define {{CASSANDRA_CONF}} in a similar way. Another option would be to load {{cassandra.in.sh}} before sourcing {{cassandra-env.sh}}, but I don't think this should be necessary because we're dealing with pre-defined package directories (eg. /usr/share/cassandra and /etc/cassandra), so it should be safe to define them in a static way.

> Consider reverting to CMS GC on 3.0
> -----------------------------------
>
>                 Key: CASSANDRA-10403
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10403
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Joshua McKenzie
>            Assignee: Paulo Motta
>             Fix For: 3.0.0 rc2
>
>
> Reference discussion on CASSANDRA-7486.
> For smaller heap sizes G1 appears to have some throughput/latency issues when compared to CMS. With our default max heap size at 8G on 3.0, there's a strong argument to be made for having CMS as the default for the 3.0 release.


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