[
https://issues.apache.org/jira/browse/ACCUMULO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130872#comment-13130872
]
Keith Turner edited comment on ACCUMULO-49 at 10/19/11 6:55 PM:
----------------------------------------------------------------
When testing mlock on a cluster, preallocating the stack memory caused a
"java.lang.OutOfMemoryError: unable to created new native thread" exception to
be thrown when trying to start a new java thread. This happened eventually
after a number of threads had been created.
was (Author: kturner):
When testing mlock on a cluster, preallocating the stack memory caused a
"java.lang.OutOfMemoryError: unable to created new native thread" exception to
be thrown when trying to start a new java thread.
> 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
