[
https://issues.apache.org/jira/browse/HBASE-14354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726726#comment-14726726
]
Hudson commented on HBASE-14354:
--------------------------------
FAILURE: Integrated in HBase-1.3 #144 (See
[https://builds.apache.org/job/HBase-1.3/144/])
HBASE-14354 Minor improvements for usage of the mlock agent (esteban: rev
1b5fb8193e0b0ffb817658fff182b84ff6e84be8)
* bin/hbase-config.sh
> 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
> Fix For: 2.0.0, 1.3.0, 0.98.15, 1.2.1, 1.1.3
>
> Attachments:
> 0001-HBASE-14354-Minor-improvements-for-usage-of-the-mloc.patch,
> HBASE-14354.v1.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)
