[
https://issues.apache.org/jira/browse/ACCUMULO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130897#comment-13130897
]
Keith Turner commented on ACCUMULO-49:
--------------------------------------
There is no memory leak. The pages in the page table that correspond to the
new threads stack are allocated when mlock is used. Without mlock, a range in
the page table is reserved for the thread but only a few pages are actually
allocated. More pages are allocated as the stack grows. So if you mlock 200M
for a process and have a 1M stack, then you could only create 200 threads max
before getting an error (its actually less threads when accounting for memory
used by heap and overhead). If using the Java -Xss options, then you can lower
the max stack size. We set this to 128k, instead of 1M.
> 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
