Actions
Bug #6086
closed
[API] Creating new job sometimes takes too long
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
-
Story points:
1.0
Description
We have been seeing a lot of timeouts in the java sdk when it is attempting to create a job. The Java SDK uses a default read timeout of 20 seconds, so this suggests that sometimes it is taking longer than 20 seconds to complete the processing associated with creating a job prior to sending a response. In addition to the short term fix of increasing the Java sdk timeout in #6071, we should investigate why job creation is taking so long.
Updated by
Updated by Brett Smith almost 9 years ago
- Project changed from 35 to Arvados
- Category set to API
- Target version changed from Bug Triage to 2015-06-10 sprint
- Story points set to 1.0
Updated by Brett Smith almost 9 years ago
I am currently leaving this on the 2015-06-10 sprint. Currently we believe that #6071 will be enough of a workaround for customer pipelines, but if it's not, I want this handy to steal and do as part of #6068.
If it doesn't come up again, it's not expected to be dealt with this sprint.
Updated by Brett Smith almost 9 years ago
- Target version changed from 2015-06-10 sprint to Arvados Future Sprints
Updated by Tom Clegg about 7 years ago
- Target version deleted (
Arvados Future Sprints)
Actions