[torquedev] [Bug 52] New: Scheduler locking support

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Mon Apr 19 03:47:44 MDT 2010


http://www.clusterresources.com/bugzilla/show_bug.cgi?id=52

           Summary: Scheduler locking support
           Product: TORQUE
           Version: 2.4.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: pbs_server
        AssignedTo: glen.beane at gmail.com
        ReportedBy: SimonT at mail.muni.cz
                CC: torquedev at supercluster.org
   Estimated Hours: 0.0


Created an attachment (id=26)
 --> (http://www.clusterresources.com/bugzilla/attachment.cgi?id=26)
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
blocked.

When no lock is present, the system behaves as if no locking mechanism exists.

-- 
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the torquedev mailing list