On 11/9/06, Fabrice Bouye <FabriceB@xxxxxxx> wrote:
Hello,
another issue we've encountered so far with condor 6.8.1 : when a job is only submitted once or twice, it seems it stays idle for a long time. However, if the very same job is submitted multiple times (three times or more), all instanced get dispatched quite quickly to execution nodes and all get executed OK.
Hi Fabrice,
Incidentally I am having the same problem on my pool; if I set the queue parameter in the submit file to be at least 10 the jobs are executed properly. After a bit of Google searching I found a possible reason for this happening--that with a single job it is automatically sent to the machine that submitted the job [ i.e. the local machine] which is having problems. Which is ironic because you would think the local machine to be able to execute jobs itself rather than the more complex transfer of files/executables to the nodes in the pool. I haven't yet figured out the solution but would like to hear a response.
What kind of jobs are you sending? Have you tried submitting a single job in the vanilla universe to see if it works?
Emily
_______________________________________________ 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 either https://lists.cs.wisc.edu/archive/condor-users/ http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com |