New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow piped commands to timeout #1875

Closed
fnothaft opened this Issue Jan 16, 2018 · 0 comments

Comments

1 participant
@fnothaft
Member

fnothaft commented Jan 16, 2018

This is useful for some commands where runtime is not consistent across all regions.

@fnothaft fnothaft added this to the 0.24.0 milestone Jan 16, 2018

@fnothaft fnothaft self-assigned this Jan 16, 2018

fnothaft added a commit to fnothaft/adam that referenced this issue Jan 22, 2018

[ADAM-1875] Add ability to timeout a piped command.
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 added a commit to fnothaft/adam that referenced this issue Jan 22, 2018

[ADAM-1875] Add ability to timeout a piped command.
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 added a commit to fnothaft/adam that referenced this issue Jan 24, 2018

[ADAM-1875] Add ability to timeout a piped command.
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 added a commit to fnothaft/adam that referenced this issue Jan 24, 2018

[ADAM-1875] Add ability to timeout a piped command.
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

[ADAM-1875] Add ability to timeout a piped command.
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.

@heuermh heuermh added this to Completed in Release 0.24.0 Feb 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment