aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Brazil <brian.bra...@boxever.com>
Subject Re: Health Checks for Updates design review
Date Fri, 03 Jul 2015 09:53:33 GMT
On 2 July 2015 at 19:16, Maxim Khutornenko <maxim@apache.org> wrote:

> Hi Brian,
>
> This feature is on a back burner for now. It’s unlikely that we'll
> make any progress within the next few months.
>
> The design is mostly hashed out at this point, so if you feel you
> could contribute or even better take it over completely it would be
> absolutely awesome!
>

Thanks for the update, unfortunately that whole feature is a bit big for me
to chew off all of anytime soon.

Yours,
Brian


>
> Thanks,
> Maxim
>
> On Thu, Jul 2, 2015 at 9:27 AM, Brian Brazil <brian.brazil@boxever.com>
> wrote:
> > On 5 May 2015 at 21:24, Maxim Khutornenko <maxim@apache.org> wrote:
> >
> >> Hi,
> >>
> >> I have put together a design proposal for improving health-enabled job
> >> update performance. Please, review and leave your comments:
> >>
> >>
> >>
> https://docs.google.com/document/d/1ZdgW8S4xMhvKW7iQUX99xZm10NXSxEWR0a-21FP5d94/edit
> >
> >
> > Hi,
> >
> > I'm looking to move some of our production jobs to Aurora, and this
> design
> > is of interest as I want to allow slack in startup and for a few failures
> > without greatly increasing update times.
> > Is there a rough ETA for this, or maybe some smaller tasks I could help
> > with? 1224 sounds easy for example, and I've already worked with that
> code.
> >
> > Thanks,
> > Brian
> >
> >
> >>
> >>
> >> Thanks,
> >> Maxim
> >>
>

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