Bugzilla – Bug 52
Scheduler locking support
Last modified: 2010-09-14 22:43:46 MDT
You need to
before you can comment on or make changes to this bug.
Created an attachment (id=26) [details]
Patch against current 2.4-fixes head
Scheduler locking is a locking technique to prevent several schedulers (or even
one scheduler, when interacting with user tools) connected to one server to
negatively impact each others performance.
New PBS Batch command is implemented with 3 subcommands:
-> acquire lock (fails if another lock is present)
-> refresh lock (refresh the lock timeout)
-> release lock (release the lock)
When a lock is present on the server, PBS batch commands are processed
depending on their category. Commands that are read-only, or work with jobs
that are not in queued state are passed through, commands that affect queued
jobs are either deferred (run immediately when the lock is released), or
When no lock is present, the system behaves as if no locking mechanism exists.
it this new feature going to get merged into trunk? any thoughts from other
The idea sounds reasonable enough.