You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Alex Newman (JIRA)" <ji...@apache.org> on 2012/05/22 23:30:40 UTC

[jira] [Assigned] (HBASE-2750) Add sanity check for system configs in hbase-daemon wrapper

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

Alex Newman reassigned HBASE-2750:
----------------------------------

    Assignee:     (was: Alex Newman)
    
> Add sanity check for system configs in hbase-daemon wrapper
> -----------------------------------------------------------
>
>                 Key: HBASE-2750
>                 URL: https://issues.apache.org/jira/browse/HBASE-2750
>             Project: HBase
>          Issue Type: New Feature
>          Components: scripts
>    Affects Versions: 0.90.0
>            Reporter: Todd Lipcon
>            Priority: Minor
>              Labels: noob
>
> We should add a config variable like MIN_ULIMIT_TO_START in hbase-env.sh. If the daemon script finds ulimit < this value, it will print a warning and refuse to start. We can make the default set to 0 so that this doesn't affect non-production clusters, but in the tuning guide recommend that people change it to the expected ulimit.
> (I've seen it happen all the time where people configure ulimit on some nodes, add a new node to the cluster, and forgot to re-tune it on the new one, and then that new one borks the whole cluster when it joins)

--
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