Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 24 Jun 2012 14:55:43 +0000 (UTC)
From: "Matteo Bertozzi (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1080721025.48853.1340549743125.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1475940858.24106.1315948628919.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4391) Add ability to start RS as root and
 call mlockall
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matteo Bertozzi commented on HBASE-4391:
----------------------------------------

{code}
$ mvn package -DskipTests -Pnative
$ ls ./hbase-server/target/native/libmlockall_agent.so
{code}

or if you use assembly:assembly
in ./target/hbase-0.95-SNAPSHOT.tar.gz 
under hbase-0.95-SNAPSHOT/native folder there's the libmlockall_agent.so
                
> Add ability to start RS as root and call mlockall
> -------------------------------------------------
>
>                 Key: HBASE-4391
>                 URL: https://issues.apache.org/jira/browse/HBASE-4391
>             Project: HBase
>          Issue Type: New Feature
>          Components: regionserver
>    Affects Versions: 0.94.0
>            Reporter: Todd Lipcon
>            Assignee: Matteo Bertozzi
>             Fix For: 0.96.0
>
>         Attachments: HBASE-4391-v0.patch, HBASE-4391-v1.patch, HBASE-4391-v2.patch
>
>
> A common issue we've seen in practice is that users oversubscribe their region servers with too many MR tasks, etc. As soon as the machine starts swapping, the RS grinds to a halt, loses ZK session, aborts, etc.
> This can be combatted by starting the RS as root, calling mlockall(), and then setuid down to the hbase user. We should not require this, but we should provide it as an option.

--
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