[
https://issues.apache.org/jira/browse/HBASE-14354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726213#comment-14726213
]
Sean Busbey commented on HBASE-14354:
-------------------------------------
hbase-config.sh doesn't parse after the patch due to this if getting folded
into a comment:
{code}
+# Verify if hbase has the mlock agentif [ "$HBASE_REGIONSERVER_MLOCK" = "true"
]; then
+ MLOCK_AGENT="$HBASE_HOME/lib/native/libmlockall_agent.so"
{code}
> Minor improvements for usage of the mlock agent
> -----------------------------------------------
>
> Key: HBASE-14354
> URL: https://issues.apache.org/jira/browse/HBASE-14354
> Project: HBase
> Issue Type: Bug
> Components: hbase, regionserver
> Reporter: Esteban Gutierrez
> Assignee: Esteban Gutierrez
> Priority: Trivial
> Attachments:
> 0001-HBASE-14354-Minor-improvements-for-usage-of-the-mloc.patch
>
>
> 1. MLOCK_AGENT points to the wrong path in hbase-config.sh
> When the mlock agent is build, the binary is installed under
> $HBASE_HOME/lib/native and not under $HBASE_HOME/native
> 2. By default we pass $HBASE_REGIONSERVER_UID to the agent options which
> causes the mlock agent to attempt to do a setuid in order to mlock the memory
> of the RS process. We should only pass that user if specified in the
> environment, not by default. (the agent currently handles that gracefully)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
