[
https://issues.apache.org/jira/browse/ACCUMULO-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538157#comment-14538157
]
Mike Drob commented on ACCUMULO-3793:
-------------------------------------
Implementation note: the typical way things like this are handled is something
like
{code}
NUMACTL=$(which numactl)
$NUMACTL command
{code}
If {{numactl}} isn't found, then the variable will be empty, and things will
still execute normally. You'll want to optionally add your flags, or check if
the variable is already set to allow operators to easily disable it.
> enable numa memory interleaving
> -------------------------------
>
> Key: ACCUMULO-3793
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3793
> Project: Accumulo
> Issue Type: Improvement
> Components: scripts
> Environment: Large VM
> Reporter: Eric Newton
> Assignee: Eric Newton
> Fix For: 1.6.3, 1.8.0, 1.7.1
>
>
> In this [fine article|http://tinyurl.com/m8lt7v2] it is recommended that NUMA
> optimizations be disabled. This seems to be exactly our use-case as well, and
> we have been struggling with ways to manage the linux page cache on large
> production systems. Do this by default in the start scripts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
