Project

General

Profile

Bug #20289

understand timeout/empty reply from server for dag submission

Added by Dennis Box 11 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
07/06/2018
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

See INC000000957470

jobsub_submit --MaxConncurrent 1000 -N 10000 sometimes returns HTTP response:100 PyCurl Error 52: Empty reply from server, but the job was successfully submitted.

See if this can be reproduced, start by inserting sleep commands at various places on a jobsub dev server.

Understand if there is a better way to handle timeouts of this type

History

#1 Updated by Dennis Box 11 months ago

also, is --maxConcurrent parameter passed to condor_submit_dag in the best way?

#2 Updated by Dennis Box 8 months ago

  • Target version changed from v1.2.8 to v1.2.8.1

#3 Updated by Dennis Box 8 months ago

  • Target version changed from v1.2.8.1 to v1.2.9

#4 Updated by Dennis Box 6 months ago

  • Target version changed from v1.2.9 to v1.3


Also available in: Atom PDF