Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of yasumoto7@gmail.com designates
 209.85.192.181 as permitted sender)
From: Joseph Smith <yasumoto7@gmail.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_3C8B902B-465E-4EE4-919D-7DAB26E26635"
Message-Id: <EC6F4C95-66FB-44A5-A90B-3DFC9E69B99E@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: time constraint on aurora jobs?
Date: Tue, 24 Feb 2015 23:45:48 -0800
References: 
 <CAMRQh+bn+6ZcAyhSqcfRMhX2bYSM0Vb1wkBi1NS+nOup0rS55Q@mail.gmail.com>
To: dev@aurora.incubator.apache.org
In-Reply-To: 
 <CAMRQh+bn+6ZcAyhSqcfRMhX2bYSM0Vb1wkBi1NS+nOup0rS55Q@mail.gmail.com>

--Apple-Mail=_3C8B902B-465E-4EE4-919D-7DAB26E26635
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Very good question.. to my knowledge there is not a =E2=80=98time=E2=80=99=
 constraint.

However, you could implement this in a few ways. One of my first =
thoughts is to setup a custom StatusChecker =
<https://github.com/apache/incubator-aurora/blob/e6e7e53d92b52d78960824022=
bef8a0546002180/src/main/python/apache/aurora/executor/common/status_check=
er.py#L68> which checks the length of a task's runtime. StatusCheckers =
can return an ExitState =
<https://github.com/apache/incubator-aurora/blob/e6e7e53d92b52d78960824022=
bef8a0546002180/src/main/python/apache/aurora/executor/common/status_check=
er.py#L27> which can end a task. FAILED will allow a Service() to be =
restarted, but KILLED should (if I=E2=80=99m following right) actually =
prevent that from being rescheduled unless a user manually reschedules =
it, which may or may not be what you=E2=80=99re looking for.

An example of this is the HealthChecker =
<https://github.com/apache/incubator-aurora/blob/467bc56049cc775eaf61520a4=
64b363d44023024/src/main/python/apache/aurora/executor/common/health_check=
er.py>, which causes a task to go into =E2=80=98FAILED=E2=80=99 if it =
does not pass a specified health check.

Please let me know if that makes sense!
Joe

> On Feb 24, 2015, at 19:11, Yuan <yuans4yrnn@gmail.com> wrote:
>=20
> Hello,
>=20
>    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?
>=20
> Thanks,
> Yuan


--Apple-Mail=_3C8B902B-465E-4EE4-919D-7DAB26E26635--