Re: [Condor-users] Problems when jobs are submitted through WebServices

[Matthew Farrellee <matt@xxxxxxxxxxx>]

On Jun 15, 2007, at 7:31 PM, Esh Esh wrote:

> Hi all,
>
> I am notice a difference in behavior of condor between the jobs  
> submitted using webservices and jobs submitted in the command  
> prompt using 'condor _submit'. If anybody has faced this problem  
> and know a solution for this, please let me know.
>
> Issue 1:
>
> Jobs submitted using condor_submit runs immediately, whereas the  
> same job when submitted using webservices is put on hold for a long  
> time (say 10 mins) and then runs, a condor_reschedule command,  
> makes the job run immediately. Why is this happeneing/

condor_submit essentially does a condor_reschedule after submitting  
jobs, you can do the same thing with the SOAP RequestReschedule call.

btw, the jobs aren't on hold they are just waiting for a negotiation  
cycle.


> Issue 2:
>
> Jobs subbmited using condor_submit once they are complete doesnt  
> get listed when condor_q is issued to condor, whereas the same job  
> when submited usiing webservices gets listed with 'C' as status,  
> further when it is removed it get listed with 'x'. This isn't  
> affecting anything, but just curious to know the behavior.

you should call CloseSpool on jobs that you are done with, if they do  
not stay in the queue after completion all their output would be  
immediately deleted and you would not have access to it via GetFile/ 
ListSpool.

you can change how long this happens with the config macro  
SOAP_LEAVE_IN_QUEUE

	http://www.cs.wisc.edu/condor/manual/v6.9.3/3_3Configuration.html#15707

useful:

	http://www.cs.wisc.edu/condor/manual/ 
v6.9.3/4_4Application_Program.html#SECTION00541300000000000000


> Issue 3:
>
> GetEnv = 'TRUE' passes all the environemnt settings for the jobs  
> submitted using 'condor_submit' but for the jobs submitted using  
> webservices, this doesnt work with 'ClassAd'. Is the name of this  
> particular ClassAdAttribute different from the 'GetEnv' mentioned  
> in the .sub file?

the attribute is called Env -- condor_submit does a lot of  
translation from what you call things in the .sub file to what is  
actually in a job's ad


> Issue 4:
>
> I have noticed some difference in the attribute names between  
> the .sub file and the ClassAd file, such as
> "Log" in .sub file maps to "UserLog" in ClassAd
> "log_xml" in .sub file maps to 'UserLogUseXml" in ClassAd
> "output" in .sub file maps to "out' in classad
> "Error" in .sub file maps to "err" in classad
> etc....
>
> Is there a place when this mapping is listed?

not really. you can always do a condor_q -l if you are curious about  
what the ads actually contain and most translations should be fairly  
obvious.

maybe, but incomplete:

	http://www.cs.wisc.edu/condor/manual/ 
v6.9.3/2_5Submitting_Job.html#SECTION00352200000000000000


best,


matt

> Thanks,
> -Esh.
>
>
>
> On 6/15/07, Esh Esh <eshforcondor@xxxxxxxxx > wrote:Hi all,
>
>
> I am using Condor 6.8.5 on
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx  
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/