Get via saga a node where slurm sent job

34 views
Skip to first unread message

Anna Kostikova

unread,
Aug 11, 2014, 1:11:00 PM8/11/14
to saga-...@googlegroups.com
Dear list,

How can I via saga identify on which node slurm has sent a job?

Thanks a lot,
Anna

Andre Merzky

unread,
Aug 11, 2014, 4:50:30 PM8/11/14
to saga-...@googlegroups.com
Hi Anna,

scontrol returns something like this for a 64-core job:

login1$ scontrol show job 3877912
JobId=3877912 Name=SAGAPythonSLURMJob
UserId=tg803521(803521) GroupId=G-81625(81625)
Priority=266 Account=TG-MCB090174 QOS=normal
JobState=PENDING Reason=PartitionDown Dependency=(null)
Requeue=0 Restarts=0 BatchFlag=1 ExitCode=0:0
RunTime=00:00:00 TimeLimit=00:15:00 TimeMin=N/A
SubmitTime=2014-08-11T15:45:11 EligibleTime=2014-08-11T15:45:11
StartTime=Unknown EndTime=Unknown
PreemptTime=None SuspendTime=None SecsPreSuspend=0
Partition=normal AllocNode:Sid=login3:20630
ReqNodeList=(null) ExcNodeList=(null)
NodeList=(null)
NumNodes=2 NumCPUs=64 CPUs/Task=1 ReqS:C:T=*:*:*
MinCPUsNode=1 MinMemoryNode=0 MinTmpDiskNode=0
Features=(null) Gres=(null) Reservation=(null)
Shared=0 Contiguous=0 Licenses=(null) Network=(null)
Command=(null)
WorkDir=/home1/01083/tg803521/radical.pilot.sandbox/pilot-53e92b3974df9236f98dd8c3

I am not sure if that contains the information you are interested in?
If so, which exactly would it be? If not, I am not sure how to
convince slurm to reveal more details...

Either way, once we find the details you are looking for, we should be
able to attach that as attributes to the saga.Job instance.

Best, Andre.
> --
> You received this message because you are subscribed to the Google Groups "saga-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to saga-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
It was a sad and disappointing day when I discovered that my Universal
Remote Control did not, in fact, control the Universe. (Not even
remotely.)

trollius

unread,
Oct 15, 2014, 4:05:59 PM10/15/14
to saga-...@googlegroups.com
Hello Andre,

Our guess is that we need an option "execution_hosts", which is not yet implemented according to the documentation 
http://saga-python.readthedocs.org/en/latest/adaptors/saga.adaptor.slurm_job.html  --> # print "Exec. hosts : %s" % (touchjob_clone.execution_hosts) # not impl.
the result is always null: "Exec. hosts : (null)"

What do you think?

Anna

trollius

unread,
Oct 15, 2014, 4:06:23 PM10/15/14
to saga-...@googlegroups.com
Hello Andre,

Our guess is that we need an option "execution_hosts", which is not yet implemented according to the documentation 
http://saga-python.readthedocs.org/en/latest/adaptors/saga.adaptor.slurm_job.html  --> # print "Exec. hosts : %s" % (touchjob_clone.execution_hosts) # not impl.
the result is always null: "Exec. hosts : (null)"

What do you think?

Anna


Ole Weidner

unread,
Oct 16, 2014, 4:19:21 AM10/16/14
to saga-...@googlegroups.com
Hi Anna,

can you please open a ticket for this at https://github.com/radical-cybertools/saga-python/issues? We’d be glad to implement this for the next release. 

Best,
Ole
signature.asc

Anna Kostikova

unread,
Oct 16, 2014, 4:53:37 AM10/16/14
to saga-...@googlegroups.com
Thanks a lot, Ole. Done

Anna
Reply all
Reply to author
Forward
0 new messages