You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/05/12 05:47:16 UTC

[jira] [Resolved] (HBASE-8926) Do not set default GC options in hbase-env.sh

     [ https://issues.apache.org/jira/browse/HBASE-8926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-8926.
-----------------------------------

    Resolution: Not a Problem

Resolving as not a problem as there isn't a strong motivation to change the defaults

> 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
>            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 was sent by Atlassian JIRA
(v6.2#6252)