hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-2750) Add sanity check for system configs in hbase-daemon wrapper
Date Sun, 08 Jun 2014 21:59:03 GMT

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

Andrew Purtell resolved HBASE-2750.

    Resolution: Won't Fix

Stale issue. Reopen if still relevant (if there's new activity)

> 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 was sent by Atlassian JIRA

View raw message