+1 (non-binding), I was testing 0.14.0 on own cluster
2016-06-14 14:34 GMT+02:00 Jake Farrell :
> +1
>
> -Jake
>
> On Fri, Jun 10, 2016 at 10:23 AM, Stephan Erb wrote:
>
> > All,
> >
> > I propose that we accept the following release candidate as the
> >
thought the log open() call would fail, and the scheduler
> process would exit (giving a strong signal that the scheduler is not
> healthy).
>
> On Fri, Jun 17, 2016 at 2:44 AM, Martin Hrabovčin <
> martin.hrabov...@gmail.com> wrote:
>
> > Hello,
> >
> > I
Hello,
I was asking same question in #aurora channel and I still haven't found an
answer so I am bringing this in mailing list with a proposal.
Is there a way to check the state of mesos-log (whether the its writable in
VOTING state) through some HTTP check outside of aurora process on a
s under the impression that holes in the
> log were filled before open() returned. Have you observed otherwise?
>
> On Wed, Jun 22, 2016 at 8:02 AM, Martin Hrabovčin <
> martin.hrabov...@gmail.com> wrote:
>
> > If there is some obvious issue with replicated log then open
+1 (non-binding)
Verified using ./build-support/release/verify-release-candidate 0.16.0-rc2
2016-09-23 2:29 GMT+02:00 Jake Farrell :
> not a blocker for the release candidate, can update the CHANGELOG in trunk
> and fix version on the ticket
>
> -Jake
>
> On Thu, Sep 22,