Timeout hit even though no timeout was specifiedSee original GitHub issue
In dsub 0.3.4, I just ran into an issue where I had a job running for a week that was terminated, saying
Failure message: User specified operation timeout reached.
However, I didn’t specify a
--timeout for this job. Looking at the docs and the user-facing code, I don’t see any place where a default timeout is set. Is there silently a default of 1 week if no
--timeout is set?
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
Hi @carbocation .
The default is indeed 7 days.
There is a command-line flag
google_v2.add_argument( '--timeout', help="""The maximum amount of time to give the pipeline to complete. This includes the time spent waiting for a worker to be allocated. Time can be listed using a number followed by a unit. Supported units are s (seconds), m (minutes), h (hours), d (days), w (weeks). Example: '7d' (7 days).""")
The docs have been updated, closing out.