Project

General

Profile

Feature #6644

Support dynamic connection lifetime between client and the server

Added by Parag Mhashilkar over 5 years ago. Updated 6 months ago.

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

0%

Estimated time:
Stakeholders:
Duration:

Description

Currently client sets the CURL_TIMEOUT to 30 sec. This results in the max connection time to stay active to be 30 sec. This fixed timeout doesn't work when dealing with server side tasks that can take long. For example, when compressing a sandbox, submitting several hundred jobs, queering a busy schedd, etc.

We need a means to support dynamic connection lifetimes that handle timeouts more gracefully.

Possible approach involves some combination of following changes

  • Change CURL_TIMEOUT to something large like 10 min or not use this at all. Client times out the connection using CURLOPT_LOW_SPEED_TIME and CURLOPT_LOW_SPEED_LIMIT
  • Server periodically sends busy status to the client that client understands and displays the info on the screen appropriately. We may need to use CURLOPT_XFERINFOFUNCTION/CURLOPT_PROGRESSFUNCTION for this.

History

#1 Updated by Parag Mhashilkar over 5 years ago

  • Target version deleted (v1.0)

#2 Updated by Parag Mhashilkar almost 5 years ago

  • Target version set to v1.2

#3 Updated by Dennis Box almost 4 years ago

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

#4 Updated by Dennis Box 6 months ago

  • Target version changed from v1.3 to v1.3.3
  • Assignee changed from Parag Mhashilkar to Dennis Box


Also available in: Atom PDF