Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: <CAFp_NitU7rsRTwXXV2RqohO1mWPoxFoHMeBE=6OgybDR8aDe5g@mail.gmail.com>
References: <CAOW5sYbvey3BWcboBfzbyOoL2tbgDKx1CNah9V=-Zmt_WHE0pw@mail.gmail.com>
 <CAM+cpfcZapM88D_56=AndbZDw55=k-O2AJYnu1uAj_L8x-Bwtg@mail.gmail.com>
 <CANntcz5t-08aERuyQxWU1j3L-1UZSv1-UcinWaVyzUQ-DO3bvg@mail.gmail.com> <CAFp_NitU7rsRTwXXV2RqohO1mWPoxFoHMeBE=6OgybDR8aDe5g@mail.gmail.com>
From: Neil Conway <neil.conway@gmail.com>
Date: Mon, 23 Jan 2017 11:49:09 -0800
Message-ID: <CAOW5sYZZ-GgTPnD04Fussf5gCi7K3_qJXO1-bjq6Aoabd7bwiQ@mail.gmail.com>
Subject: Re: Disallowing pre-1.0 Mesos agents
To: dev <dev@mesos.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Mon, 23 Jan 2017 19:49:16 -0000

Right -- I'll add a note to that effect to the CHANGELOG for 1.3.0.

Neil

On Fri, Jan 20, 2017 at 7:11 PM, Benjamin Mahler <bmahler@apache.org> wrote:
> +1
>
> Thanks for taking on the explicit rejection, much needed safety
> improvement. If we state that a Mesos 1.3.0 master will not support pre-1.0
> agents, it seems to carry an implication that we supported 1.2 and 1.1
> having pre-1.0 agents. While it might work, we should clarify for users per
> vinod's comment.
>
> On Fri, Jan 20, 2017 at 12:45 PM, Vinod Kone <vinodkone@apache.org> wrote:
>
>> +1
>>
>> Technically 0.28.0 was only supposed to be compatible with 0.27.0 and 1.0.
>>
>>
>> On Fri, Jan 20, 2017 at 8:02 PM, Zameer Manji <zmanji@apache.org> wrote:
>>
>> > +1
>> >
>> >
>> >
>> > On Fri, Jan 20, 2017 at 10:58 AM, Neil Conway <neil.conway@gmail.com>
>> > wrote:
>> >
>> > > I'd like to propose that the Mesos 1.3.0 should not allow pre-1.0
>> > > Mesos agents to register.
>> > >
>> > > Motivation:
>> > >
>> > > (1) We can simplify the master code in a few places. For example, we
>> > > can assume that we always have a FrameworkInfo for any task running on
>> > > a registered agent. Needing to handle running tasks without a
>> > > FrameworkInfo makes the code unreadable and has been a source of bugs.
>> > >
>> > > (2) The master only needs to report "orphan tasks" and "unregistered
>> > > frameworks" if the cluster contains pre-1.0 agents. If we disallow
>> > > such agents, we can remove the code for computing these fields in the
>> > > HTTP endpoints and elsewhere. (We'll probably still need to keep the
>> > > actual fields in the JSON/protobuf output for backward compatibility,
>> > > but they will always be empty.) We can also remove "orphan tasks" from
>> > > the web UI.
>> > >
>> > > In addition to declaring that Mesos 1.3.0 masters will not support
>> > > pre-1.0 Mesos agents in the CHANGELOG, it seems safer to me to
>> > > disallow such agents from registering.
>> > >
>> > > Comments welcome.
>> > >
>> > > Thanks,
>> > > Neil
>> > >
>> > > --
>> > > Zameer Manji
>> > >
>> >
>>