Hi Martin,

  I am using gt4.0.6 on the client node.  I didn't try with Fork.  Let me see 
how Fork behaves.  Thanks.

Prakashan



-----Original Message-----
From: Martin Feller [mailto:[EMAIL PROTECTED]
Sent: Tue 5/27/2008 9:48 AM
To: Korambath, Prakashan
Cc: gt-user; Jin, Kejian; Korambath, Prakashan
Subject: Re: [gt-user] Globus GRAM reporting status for each task in a SGE 
job-job array submission
 
Prakashan:

GRAM should send a Done notification if the last job is done, and not when
the first job is done. I tried it here and it works as expected for me.
What GT version are you using?
This is probably not at all SGE related, but does it behave in the same way
when you submit to, say, Fork instead of SGE?

Martin


----- Original Message -----
From: "Prakashan Korambath" <[EMAIL PROTECTED]>
To: "gt-user" <[email protected]>, "Kejian Jin" <[EMAIL PROTECTED]>, 
"Prakashan Korambath" <[EMAIL PROTECTED]>
Sent: Monday, May 26, 2008 4:10:46 PM GMT -06:00 US/Canada Central
Subject: [gt-user] Globus GRAM reporting status for each task in a SGE job-job 
array submission




Hi, 

We noticed that Globus GRAM status reporting service (eg: globusrun-ws -status 
-j job_epr) reports status as 'Done' immediately when first few tasks in a 
job-array (multi jobs) are completed. Is there a way to make it wait until the 
last task in the job array is completed? It is ok if all tasks are completed 
within few seconds apart, but in most cases they are not and globus reports the 
entire job is finished based on perhaps the reading from 
$SGE_ROOT/common/reporting file when there are still tasks waiting to be run. 
If there is an option to query the status of the last task in a job array it 
would be nice. Thanks. 


Prakashan Korambath 

Reply via email to