[
https://issues.apache.org/jira/browse/HBASE-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437470#comment-13437470
]
Matteo Bertozzi commented on HBASE-6567:
----------------------------------------
@stack the patch contains also the hbase-env.sh with the two new variables a
comment that try to explain what the mlock is used for, but doesn't seems to be
in trunk. Do you think is not useful to expose that? (I've no strong opinion on
expose it or not, since most of the user can live without knowing it)
{code}
+# Uncomment and adjust to keep all the Region Server pages mapped to be memory
resident
+#HBASE_REGIONSERVER_MLOCK=true
+#HBASE_REGIONSERVER_UID="hbase"
{code}
> make memory locking configuration of regioservers more flexible
> ---------------------------------------------------------------
>
> Key: HBASE-6567
> URL: https://issues.apache.org/jira/browse/HBASE-6567
> Project: HBase
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 0.96.0
> Reporter: Roman Shaposhnik
> Assignee: Matteo Bertozzi
> Fix For: 0.96.0
>
> Attachments: HBASE-6567-v0.patch
>
>
> The current implementation of the memory locking feature of regisoservers has
> a downside of not being flexible to configure for permanent use. Sure there
> is a --mlock flag but that needs to be explicitly passed on every invocation
> and thus require extra steps to be configured for permanent use (IOW, there's
> not a single env variable I can set to have a desired effect). The only other
> alternative -- the explicit setting of HBASE_REGIONSERVER_OPTS -- has a
> downside of being pretty cryptic to the novice user and has a killer problem
> of not explicitly telling higher level scripts (like init.d or upstart ones)
> which user the initial hbase process should be executed as.
> I propose a very simple solution (which is essentially making --mlock setting
> into an env. variable): add a variable called HBASE_REGIONSERVER_MLOCK that
> can be set in hbase-env.sh and has the following semantics:
> * [default] not set: mlocking feature is disabled
> * set but empty: mlocking feature is enabled and the target user is hbase
> * set and not empty: mlocking feature is enabled and the target user is
> the value of the variable
> Thoughts?
--
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
