How to get all cgroup cpuset cores with singlejob policy job submissions (without specifying procs)


After upgrading to Torque 6.0.x with cgroups enabled, jobs submitted with "-l nodes=1,naccesspolicy=singlejob" get restricted to one core because that's what gets assigned to the cpuset, despite the job being the only one on the node.

Previously, jobs submitted with singlejob or -n (node-exclusive) could access all resources on the compute node. We understand that this is the purpose of cgroups, but we still need a way to enable support for the previous behavior (for legacy scripts).



Upgrade to Moab 9.0.2 and Torque 6.0.2, and set the following parameter in moab.cfg:

RMCFG[<your Torque name>] FLAGS=MigrateAllJobAttributes

This will enable full assignment of cores to the cgroup's cpuset for any jobs submitted with the following syntaxes (these all apply for both qsub and msub):

  • -l naccesspolicy=singlejob
  • -W x=naccesspolicy=singlejob
  • -n
  • msub and MWS jobs that get singlejob applied via policy, template, etc.


* Jobs submitted with -n will automatically get all node cores assigned to the cgroup cpuset(s), regardless of requested ppn. Jobs that specify singlejob, but do NOT include -n, will get the number of cores stated on the ppn.

* This method has been provided as a bridge. Future scripts should use the -L NUMA Resource Request syntax, described here:

Example: qsub -L tasks=1:lprocs=all:place=node

* This method supplants the deprecated "allprocs" job submission flag, which Moab does not support for full cpuset core assignment. Until Adaptive Computing completely discontinues support for the "allprocs" flag, it will still work to assign all cores to the job, as far as Moab's tracking of the node's resources; however, it is, effectively, incompatible with systems that have configured Torque with the --enable-cgroups option.

Last update:
2016-07-12 18:59
Rick McKay
Average rating:0 (0 Votes)

You can comment this FAQ

Chuck Norris has counted to infinity. Twice.

Records in this category