Page Comparison

...

• Change Control: Public/Stable
• Summary: HUPing the scheduler will cause the scheduler to reread the usage file
• Details:
  • Current Behavior:
    • On a HUP, the scheduler will first write out its view of the fairshare usage before rereading it.  This used to be needed when the scheduler didn't write out its fairshare usage every cycle
    • If an admin makes a change via the pbsfs command, the change will be overwritten on the next scheduling cycle
    • The only way to make a change via pbsfs is to first kill the scheduler, make the change, and then restart the scheduler
  • Changed Behavior:
    • On a HUP, the scheduler will reread the usage (it won't write it out first).  If no one has modified the usage since the last scheduling cycle, the scheduler will reread the same data
    • If an admin makes a change via pbsfs, they can send the scheduler a HUP and the scheduler will see the changed usage
    • Possible race condition:
      • The admin could make a change and a cycle could overwrite the change before the they have a chance to HUP the scheduler
      • How to fix this race condition
        • Stop scheduling and (i.e., qmgr -c 'set server scheduling=False') 
        • wait for the current scheduling cycle to finish
        • Make changes to the fairshare usage via the pbsfs command
        • HUP the scheduler
        • Start scheduling 

...