Pipelines should have a non-infinite deadline

[Sanrag]

With groningen's ability to run as a service, clients can start a pipeline and forget about them. There should be a deadline (maybe modifiable by clients) after which the pipeline should be marked stale and removed from groningen.

[d2rk]

👍

[etheon]

We had talked about this previously.

Slade's idea was to institute a per user quota which made sense to me as well. Why time a pipeline out if you can make the user clean it up? Unless of course the user walks away forever.

Perhaps both should be implemented.

On Aug 29, 2013, at 2:05 PM, Sanrag Sood [email protected] wrote:

With groningen's ability to run as a service, clients can start a pipeline and forget about them. There should be a deadline (maybe modifiable by clients) after which the pipeline should be marked stale and removed from groningen.

—
Reply to this email directly or view it on GitHub.

[Sanrag]

Clients can be automated systems which may lose state that they ever started a pipeline (crash, then restart but no restoration of state). In such a case, the pipeline would keep running forever.