hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8926) Do not set default GC options in hbase-env.sh
Date Thu, 11 Jul 2013 01:27:49 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705366#comment-13705366

Enis Soztutar commented on HBASE-8926:

How are we going to default to CMS then? If G1 is used, shouldn't that setting override HBASE_OPTS
> Do not set default GC options in hbase-env.sh
> ---------------------------------------------
>                 Key: HBASE-8926
>                 URL: https://issues.apache.org/jira/browse/HBASE-8926
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0, 0.95.2, 0.94.10
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Trivial
>         Attachments: 8926.patch
> Exporting default GC options in HBASE_OPTS from hbase-env.sh by default can interfere
with some deployment scenarios. We probably shouldn't be doing that.
> Noticed this when using scripts to set up EC2 test clusters for G1 GC. Having "-XX:+UseConcMarkSweepGC"
on the command line in that case will cause the JVMs to fail to launch.

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

View raw message