[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Is a worker sub-process created for SOAP requests

1. Is there any work-around to handle collector & schedd taking too long in responding to SOAP? Is quill the solution?
2. This (SOAP not using QUERY_WORKERS) will be fixed in upcoming releases, right?


On Tuesday 04 August 2009 06:54 AM, Matthew Farrellee wrote:
sateesh.potturu@xxxxxxxxx wrote:
Hello All,

We are sometimes observing condor_schedd and condor_collector getting stuck in responding to SOAP requests; some times as high as 5 minutes. The latter caused Startd class ads to get removed as stale ads!!

Do SCHEDD_QUERY_WORKERS and COLLECTOR_QUERY_WORKERS have any impact on SOAP requests? We observed worker sub-processes getting created for a burst of 'condor_q -l' commands. But, did not observe any worker sub-processes getting created for SOAP requests. Are SOAP requests handled in the main condor_schedd/condor_collector processes itself?

IIRC, SOAP queries are handled in the main processes. I believe this is because the QUERY_WORKER capabilities are implemented within the CEDAR query functions.

I don't think there is any particular reason that the SOAP queries could not use the QUERY_WORKERS.


Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: 


Please do not print this email unless it is absolutely necessary.

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.