Page Comparison

...

• Visibility: Public
• Change Control: Stable
• Details:
  • Scheduler now has additional attributes which can be set in order to run it.
    • sched_priv - to point to the directory where scheduler keeps the fairshare usage, resource_group, holidays file and sched_config
    • sched_log - to point to the directory where scheduler logs.
    • partition - list of all the partition/s for which this scheduler is going to schedule jobs.
    • sched_host - hostname on which scheduler is running. For default scheduler it is set to pbs server hostname.
    • sched_port - port number on which scheduler is listening.
    • state - This attribute shows the status of the scheduler. It is a parameter that is set only by pbs server.
  • One can set a partition or a comma separated list of partitions to scheduler object. Once set, given scheduler object will only schedule jobs from the queues attached to specified partition"
    • qmgr -c "s sched multi_sched_1 partition='part1,part2'"
  • If no partition are specified for a given scheduler object, other than the default scheduler where no partition value can be set, then that scheduler will not schedule any jobs.
  • By default, All new queues created will be scheduled by the default scheduler, until they have been assigned to a specific partition.
  • A partition once attached to a scheduler can not be attached to a second scheduler without removing it from the first scheduler. If tried, then it will throw following error:
    • qmgr -c "s sched multi_sched_1 partition+='part2'"
      Partition part2 is already associated with scheduler <scheduler name>.
  • Scheduler object "state" attribute will show one of these 3 values  - DOWN, IDLE, SCHEDULING
    • If a scheduler object is created but scheduler is not running for some reason state will be shown as "DOWN"
    • If a scheduler is up and running but waiting for a cycle to be triggered the state will be shown as "IDLE"
    • If a scheduler is up and running and also running a scheduling cycle then the state will be shown as "SCHEDULING"
  • The default sched object is the only sched object that cannot be deleted.
  • Trying to set sched_port, sched_priv and sched_host on default scheduler will not be allowed. The following error message is thrown in server_logs when we try to change sched_priv directory.
    • qmgr -c "s sched default sched_priv = /tmp
      Operation is not permitted on default scheduler
  • Trying to start a new scheduler other than the default scheduler, without assigning a partition will throw the following error message in scheduler logs.
             Scheduler does not contain a partition

  • If Scheduler fails to accept new value for its sched_log directory then comment of the corresponding scheduler object at server is updated with the following message.  Also scheduling attribute is set to false.
            Unable to change the sched_log directory

  • If Scheduler fails to accept new value for its sched_priv directory then comment of the corresponding scheduler object at server is updated with the following message.  Also scheduling attribute is set to false.
           Unable to change the sched_priv directory

  • If PBS validation checks for new value of sched_priv directory do not pass then comment of the corresponding scheduler object at server is updated with the following message. Also scheduling attribute is set to false.
          PBS failed validation checks for sched_priv directory
  • If Scheduler is successful in accepting the new log_dir configured at qmgr then the following error message is thrown in the scheduler logs.

           Scheduler log directory is changed to <value of path of the log directory>

  • If Scheduler is successful in accepting the new sched_priv configured at qmgr then the following error message is thrown in the scheduler logs.
           Scheduler priv directory is changed to <value of path of the sched_priv directory> 

  • If we keep on disassociating partitions from a scheduler until it does not contain any of the partitions then this scheduler is identical to default scheduler in which case we shutdown this scheduler and following error message is thrown in scheduler logs.
           Scheduler does not contain a partition.   

  • If Scheduler fails in getting its stats from Server then the following error message is shown in scheduler logs.
           Unable to retrieve the scheduler attributes from server     

  • A new option -I is introduced to provide a name to a scheduler. If we run pbs_sched without this option then it is considered as default scheduler whose name is "default".
           Example: pbs_sched -I sc1 -S 15051
           Here scheduler is started on port number 15051 whose id/name is "sc1".

                                                                                                                                                                                                                                

    
    

...

• Visibility: Public
  Change Control: StableDetails:
  • PBS does not allow attributes like scheduling, scheduler_iteration to be set on PBS server object.
  • scheduling and scheduler_iteration now belong to the sched object
    • During failover when secondary server takes control it will try to connect to connect to schedulers by using their sched_host attribute.
      
      • If secondary server is unable to connect to scheduler running on remote host then it will start that scheduler locally and update it's "sched_host" attribute.
      • When Primary pbs server takes control from secondary it will always check if scheduler's sched_host attribute matches it's server name, if it doesn't then it will shutdown the remote scheduler and spawn it locally on primary server.
    • If set at the server level, the changes will be applied to the default sched object
  • As backward compatibility PBS still allows attributes like scheduling, scheduler_iteration to be set on PBS server object. Any changes made to these attributes are automatically reflected in scheduler object. Similarly if any changes are made to these attributes in scheduler object, they are automatically reflected in the server object.
  • If at any point in time if Server is not able to contact or reach the corresponding scheduler one of the following messages are shown in server_logs.
           Unable to reach scheduler associated with partition [<partition id>]
           Unable to reach scheduler associated with job <job id>

...