[
https://issues.apache.org/jira/browse/CASSANDRA-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113271#comment-13113271
]
Peter Schuller commented on CASSANDRA-3245:
-------------------------------------------
Or we could do something seemingly ugly but probably very effective and safe:
Try running "ls -d / > /dev/null" with numactl and if that fails, assume it is
because numactl isn't working. That should hopefully work in pretty much any
environment.
I'll submit a patch soonish.
> Don't fail when numactl is installed, but NUMA policies are not supported
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-3245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3245
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 1.0.0
> Environment: Any Linux system where a 'numactl' executable is
> available, but no NUMA policies are actually supported. EC2 nodes are easy
> examples of environments with no NUMA policy support.
> Reporter: paul cannon
> Assignee: Peter Schuller
> Priority: Minor
> Fix For: 1.0.0
>
>
> When numactl is installed but NUMA policies are not supported, trying to run
> cassandra gives only:
> {noformat}
> numactl: This system does not support NUMA policy
> {noformat}
> ..and the startup script fails there.
> We should probably fail a little more gracefully. Possibly the best way to
> tell if numactl will work is by using:
> {noformat}
> numactl --hardware
> {noformat}
> but I don't have ready access to a machine with proper NUMA support at the
> moment so I can't check how easy it is to tell the difference in the output.
> It looks just as reliable (if possibly a bit more brittle) to check for the
> existence of the directory {{/sys/devices/system/node}}. If that directory
> doesn't exist, we shouldn't even try to use or run numactl.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
