aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Smith <>
Subject Re: time constraint on aurora jobs?
Date Wed, 25 Feb 2015 07:45:48 GMT
Very good question.. to my knowledge there is not a ‘time’ constraint.

However, you could implement this in a few ways. One of my first thoughts is to setup a custom
StatusChecker <>
which checks the length of a task's runtime. StatusCheckers can return an ExitState <>
which can end a task. FAILED will allow a Service() to be restarted, but KILLED should (if
I’m following right) actually prevent that from being rescheduled unless a user manually
reschedules it, which may or may not be what you’re looking for.

An example of this is the HealthChecker <>,
which causes a task to go into ‘FAILED’ if it does not pass a specified health check.

Please let me know if that makes sense!

> On Feb 24, 2015, at 19:11, Yuan <> wrote:
> Hello,
>    In apache aurora, there are resource isolations and sizings on CPU,
> memory and disk space, which can be specified in the job configuration
> file. Is there any similar way to put a constraint on job running time,
> like killing a job if it has been running for more than a certain amount of
> time?
> Thanks,
> Yuan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message