Allow piped commands to timeout #1875
Closed
Comments
fnothaft
pushed a commit
to fnothaft/adam
that referenced
this issue
Jan 22, 2018
Resolves bigdatagenomics#1875. Adds an optional timeout parameter to the `GenomicRDD.pipe` function. If this is provided, a command will be killed (but without failing the Spark task) if it runs for longer than the timeout parameter.
fnothaft
pushed a commit
to fnothaft/adam
that referenced
this issue
Jan 22, 2018
Resolves bigdatagenomics#1875. Adds an optional timeout parameter to the `GenomicRDD.pipe` function. If this is provided, a command will be killed (but without failing the Spark task) if it runs for longer than the timeout parameter.
fnothaft
pushed a commit
to fnothaft/adam
that referenced
this issue
Jan 24, 2018
Resolves bigdatagenomics#1875. Adds an optional timeout parameter to the `GenomicRDD.pipe` function. If this is provided, a command will be killed (but without failing the Spark task) if it runs for longer than the timeout parameter.
fnothaft
pushed a commit
to fnothaft/adam
that referenced
this issue
Jan 24, 2018
Resolves bigdatagenomics#1875. Adds an optional timeout parameter to the `GenomicRDD.pipe` function. If this is provided, a command will be killed (but without failing the Spark task) if it runs for longer than the timeout parameter.
heuermh
added a commit
that referenced
this issue
Jan 25, 2018
Resolves #1875. Adds an optional timeout parameter to the `GenomicRDD.pipe` function. If this is provided, a command will be killed (but without failing the Spark task) if it runs for longer than the timeout parameter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is useful for some commands where runtime is not consistent across all regions.
The text was updated successfully, but these errors were encountered: