...

Parameters to prevent the queue getting too big

When the server has limited resources and cannot process the jobs in time, there is a risk of the jobs getting stacked in the queue. There are two configuration parameters that can help and can be set in Config.nmis:

• There was no default abort_plugins_after option in the configuration. This value can be added in Config.nmis:

  'overtime_schedule' => {
      'abort_plugins_after' => 7200, # Seconds
     ...
  }
  

• The schedule keeps adding these jobs into the queue. The workers can discard these jobs changing the configuration options postpone_clashing_schedule to 0.

  'postpone_clashing_schedule' => 0,
  

After theses two changes, nmis9d daemon needs to be restarted.

Interacting with the daemon using nmis-cli

...

./bin/nmis-cli act=schedule job.type=update at="now + 5 minutes" job.node=testnode job.force=1 
Job 5d3a5e2d3feeed1f19c46e55 created for node testnode (6204cd3d-3cc1-4a3a-b91e-e269eb5042a4) and type update.

# or with job.priority, job.verbosity and job.output
bin/nmis-cli act=schedule job.type=update job.priority=1 job.node=testnode job.verbosity=9 job.output=/tmp/localhost.log job.force=1

If successful nmis-cli will report the queue Id and the expanded parameters of your new job.

...