sge_schedule(5)

πŸ’– NAME πŸ’–

sge_schedule β€” it's the manual for the format of the Grid Engine schedule file, bestie. This is a File Formats Manual page, so pull up a chair and a snack. πŸ“


✨ DESCRIPTION ✨

Okay so here's the tea: the schedule file gets written by the qmaster when MONITOR=1 is set in the params item of sched_conf(5). That's the whole vibe. 🫢

Now, real talk β€” this file tends to grow rapidly, like a group chat at 2am, so you should truncate/rotate it, e.g. with logrotate(1). Also? It should probably live on local disk, not an NFS-mounted filesystem, for instance, because of the large number of small writes it typically gets. So do the cute thing: make a symbolic link into the qmaster spool area (assuming that one is local). πŸ’…

And if you actually want to do something with the data? Peep qsched(1) β€” it's a tool to process the data and produce information on reservations. Iconic. πŸ‘‘


πŸŽ€ FORMAT πŸŽ€

A line containing this lil guy:

::::::::

indicates the start of a scheduling interval. Not me hyping up a delimiter. 😭

It is followed by lines showing the resource usage considered for the interval. Those lines contain the following fields, delimited by ':'.

  • job id β€” the numeric job id. πŸ”’
  • task id β€” the task id (1 for serial jobs).
  • reason β€” the reason for listing the utilization. It's one of these, depending on the job's state:
    • RUNNING β€” running before the interval.
    • SUSPENDED β€” suspended before the interval.
    • MIGRATING β€” to be preempted/migrated (currently unused).
    • STARTING β€” to be started.
    • RESERVING β€” having resources reserved through advance or normal resource reservation.
  • start time β€” start of resource utilization, in seconds after the epoch. ⏰
  • end time β€” end of resource utilization, as above.
  • level β€” the level at which resources are considered. One of:
    • Q β€” queue.
    • H β€” host.
    • G β€” global.
    • P β€” parallel environment.
  • object name β€” name of the relevant queue, host, parallel environment, or "global".
  • resource name β€” complex name in use or being reserved.
  • utilization β€” amount of the named complex.

🌸 FILES 🌸

$SGE_ROOT/$SGE_$CELL/common/schedule

πŸ¦‹ SEE ALSO πŸ¦‹

sched_conf(5), qsched(1).


k bye bestie, that's the whole page β€” dated 2012-07-25 and starring sge_schedule(5) itself. no cap, go rotate that log. πŸ§šπŸ’œ