hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Newman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-2750) Add sanity check for system configs in hbase-daemon wrapper
Date Wed, 17 Aug 2011 23:50:28 GMT

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

Alex Newman commented on HBASE-2750:
------------------------------------

I assume it should only prevent the regionserver/master daemons from starting?

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message