[
https://issues.apache.org/jira/browse/ACCUMULO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130858#comment-13130858
]
Keith Turner commented on ACCUMULO-49:
--------------------------------------
mlockall_agent sounds pretty cool. We have experimented w/ mlock. We wrote
some JNI code, but the user had up the ulimit for it to work. One issue we ran
into is that thread stacks seem to be preallocated when mlock is enabled.
Without mlock, memory is only allocated on the stack as it is used. So w/ the
default 1M stack, each thread would allocate 1M of mem when it was created.
Used pmap to verify this. Have you had any issues w/ this?
> optionally monitor swappiness on every server
> ---------------------------------------------
>
> Key: ACCUMULO-49
> URL: https://issues.apache.org/jira/browse/ACCUMULO-49
> Project: Accumulo
> Issue Type: New Feature
> Components: logger, master, trace, tserver
> Environment: idle tablet server is swapped out on an otherwise busy
> system
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Minor
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Linux kernel will eagerly swap idle memory (such as the tablet server) for
> disk cache unless the /proc/sys/vm/swappiness setting is set to 0. A
> swapped-out server is sluggish enough that it loses its zookeeper lock.
--
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
