[ https://issues.apache.org/jira/browse/CASSANDRA-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Schuller updated CASSANDRA-3245: -------------------------------------- Attachment: 3245.txt Attaching trivial patch that does the ls test. @paul Can you test whether numactl exits with a proper non-0 exit status on the system where it is not supported? I've tested the script as such, but I don't have a system available without the necessary support to test on. > 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 > > Attachments: 3245.txt > > > 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