[torqueusers] Re: [Cluster Resources #4099] Torque resource manager
does not send "command new" to Moab scheduler
Prakash.Velayutham at cchmc.org
Mon Feb 16 12:29:12 MST 2009
I am surprised how this is a Moab issue. Why don't I see Torque
sending the "SCH_SCHEDULE_NEW" to Moab in Torque's logs, if the issue
is Moab-related? Just curious.
On Feb 16, 2009, at 2:16 PM, Douglas Wightman via RT wrote:
> This was a known regression in 5.3.1 and it has been fixed in
> snapshots since then. You can download a snapshot or wait for 5.3.2
> which will be released early this week.
> - Douglas
> ----- "Prakash Velayuthum via RT" <moab-
> support at clusterresources.com> wrote:
>> Ticket [Cluster Resources #4099] -- Ticket created by MoabCCH
>> Queue: moab-support
>> Organization: Cincinnati Children's Hospital
>> Subject: Torque resource manager does not send "command new" to
>> Moab scheduler
>> Owner: Nobody
>> Requestors: Prakash.Velayutham at cchmc.org
>> Status: new
>> Ticket <URL:
>> http://support.clusterresources.com/Ticket/Display.html?id=4099 >
>> I am using Torque 2.3.6 with Moab 5.3.1 at my site. Here is the
>> strangest thing I see.
>> When Torque RM is used with Torque scheduler, with "set server
>> scheduling = True", I see that the Torque server logs a
>> "PBS_Server;Svr;bmiclustersvcd1.cchmc.org;Scheduler sent command new"
>> message, but with Moab scheduler, everything works except a new job
>> does not trigger this somehow. So Moab schedules the job every 30
>> seconds instead of with the new job trigger.
>> Has anyone seen this? I have tested this like 10 times now and it is
>> consistent and reproducible. Every time I enable Torque scheduler,
>> jobs get scheduled immediately, but when Moab is enabled, Moab gets
>> new jobs only every 30 seconds.
>> Thanks for any ideas.
More information about the torqueusers