Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

PP-586 - Getting issue details... STATUS

Interface: alps_create_vnode_per_numa

  • Visibility: Public
  • Change Control: Experimental
  • Details:
    • alps_create_vnode_per_numa is a Boolean. Setting it to "TRUE" will cause PBS to create one vnode per Cray numa node. This is the 
      default behavior when alps_create_vnode_per_numa is not set in mom_priv/config. Setting it to "FALSE" will cause PBS to create
      one vnode per Cray compute node.
    • Naming convention of the vnodes will follow what was stated in SP16543 EDD, without the segment.
    • New interface: new mom_priv configure variable.
    • NOTE: when alps_create_vnode_per_numa is set to "FALSE", it will not be possible for PBS to schedule based on segments.


Administrator's instructions.

  • When changing from using one type of vnode create versus another, you must first:
    • Quiesce the system.
    • Remove all existing vnodes of the vntype cray_compute. The easiest way to do this is to delete all vnodes using 
      • qmgr -c "delete node @default"
    • Set the mom_priv configuration variable to desired setting in each MoM.
    • HUP the MoM.
    • Add the MoMs back using qmgr: qmgr -c "create node <mom name>"


Definition of technical terms, spelling out acronyms and abbreviations.

Technical termDescription or definition
NUMA nodes

It expands to Non Uniform Memory Access. These are the individual segments that make up a Cray compute node. There can be 1, 2 or 4 of them per Cray compute node depending on the hardware.

  • No labels