cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3245) Don't fail when numactl is installed, but NUMA policies are not supported
Date Mon, 26 Sep 2011 15:47:29 GMT


paul cannon commented on CASSANDRA-3245:

bq. @paul Can you test whether numactl exits with a proper non-0 exit status on the system
where it is not supported?

Indeed it does; using --interleave=all when there is no NUMA policy support causes an exit
value of 1.


> Don't fail when numactl is installed, but NUMA policies are not supported
> -------------------------------------------------------------------------
>                 Key: CASSANDRA-3245
>                 URL:
>             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:


View raw message