hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4391) Add ability to start RS as root and call mlockall
Date Thu, 14 Jun 2012 20:05:42 GMT

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

stack commented on HBASE-4391:

@Matteo What about Andrew's suggested location for the src and native bits?  Whats it like
when we add compile of mlockall to our compile goal in mvn?  Is it fast?  On this question:

bq. If this will be integrated in hbase, do you want to force everyone to use root or add
hbase user in limits.d to start RS? or we can add some --no-swap flag to region server start

We cannot require you be root to start hbase.  It looks like this not necessary anyways? 
If you want the mlockall facility, then you can require folks be root (or do you security.conf

The Todd trick is nice as is your tidy up.  Thanks.
> 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: Todd Lipcon
>             Fix For: 0.96.0
>         Attachments: HBASE-4391-v0.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


View raw message