Mailing-List: contact dev-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAKTzdV2T5b40Z3qQ0+K01yBy3=TfFgqbZehZ4y=qmFd-=+wafw@mail.gmail.com>
References: 
 <CAKTzdV2mOWwsxKHqjfojjhcXPuYky5z-j_YjCmzNGBvnM9R6wQ@mail.gmail.com>
 <CAMReA911P0Hi-yb_GipdTGfRs=yt25Qc+1YPN2zOSeWZD6EXVQ@mail.gmail.com>
 <CAK7Zj11DyphtYy718aLipfR0UdsRLLAPS0ErX0UdS47Z46+pqQ@mail.gmail.com>
 <6E74295B-F30E-4B23-90F6-01C0EFC03CC0@gmail.com>
 <CAMnduq_ffWJAc12pPPkB=qPowBgKHfGb1N7BuqoaBbyAASwF6A@mail.gmail.com>
 <CAKTzdV2T5b40Z3qQ0+K01yBy3=TfFgqbZehZ4y=qmFd-=+wafw@mail.gmail.com>
From: Mauricio Garavaglia <mauriciogaravaglia@gmail.com>
Date: Thu, 24 Sep 2015 01:18:55 -0300
Message-ID: 
 <CAKTzdV0TUWFq=tnUvLaUfG7g-SBoQEq2FVme=MQesV57Mj_cQg@mail.gmail.com>
Subject: Re: Upgrading from 0.7
To: dev@aurora.apache.org
Content-Type: multipart/alternative; boundary=001a11408a64dc69b40520768931

--001a11408a64dc69b40520768931
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,
I updated the executors and then rolled the schedulers (have 5 of them).
Everything went smooth, and the tasks kept running :)

On Tue, Sep 22, 2015 at 1:18 PM, Mauricio Garavaglia <
mauriciogaravaglia@gmail.com> wrote:

> Thanks for answers guys, really appreciated, I'll let you know how it goe=
s.
>
> On Mon, Sep 21, 2015 at 4:09 PM, Joshua Cohen <jcohen@twopensource.com>
> wrote:
>
>> Filed https://issues.apache.org/jira/browse/AURORA-1497 to add
>> documentation on how best to upgrade the various Aurora components.
>>
>> On Mon, Sep 21, 2015 at 12:58 PM, Joseph Smith <yasumoto7@gmail.com>
>> wrote:
>>
>> > We also shut down all of the schedulers, upgrade to the new version,
>> then
>> > bring them all back up. This isn=E2=80=99t a hard requirement, but it =
has made
>> > things a bit simpler for us in practice to always know we=E2=80=99re d=
ealing
>> with
>> > the same version of the schedulers on all hosts at once.
>> >
>> > > On Sep 21, 2015, at 10:55 AM, Zameer Manji <zmanji@apache.org> wrote=
:
>> > >
>> > > I don't think the 0.7 -> 0.9 upgrade path has been tested. I think i=
t
>> is
>> > > advisable to upgrade from 0.7 to 0.8 then later upgrade from 0.8 to
>> 0.9.
>> > I
>> > > think Jeff's upgrade steps are reasonable and shouldn't give you any
>> > > trouble. Note that upgrading the executors won't affect existing
>> tasks.
>> > If
>> > > you want the current tasks on the system to adopt the latest executo=
r
>> you
>> > > will need to upgrade the executor and then roll your tasks so they
>> can be
>> > > relaunched with the updated binary. This isn't necessary to do but
>> keep
>> > > this in mind if you are expecting tasks to leverage the latest
>> executor
>> > > functionality.
>> > >
>> > > On Sun, Sep 20, 2015 at 8:30 PM, Jeff Schroeder <
>> > jeffschroeder@computer.org>
>> > > wrote:
>> > >
>> > >> When I did this, I updated the executors, then the observers, and
>> then
>> > the
>> > >> schedulers, one at a time, in a rolling fashion. Seemed to work fin=
e,
>> > but
>> > >> the clusters were lightly utilized.
>> > >>
>> > >> On Sun, Sep 20, 2015 at 9:40 PM, Mauricio Garavaglia <
>> > >> mauriciogaravaglia@gmail.com> wrote:
>> > >>
>> > >>> Hi guys,
>> > >>>
>> > >>> I'm about to upgrade a cluster from 0.7 to 0.9 and was wondering
>> what
>> > are
>> > >>> the things to consider to make it as seamless as possible?
>> > >>>
>> > >>> For example, update the executors first and then the schedulers;
>> just
>> > >>> update the schedulers one at a time, etc.
>> > >>> Thanks!
>> > >>>
>> > >>> Mauricio
>> > >>>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Jeff Schroeder
>> > >>
>> > >> Don't drink and derive, alcohol and analysis don't mix.
>> > >> http://www.digitalprognosis.com
>> > >>
>> > >> --
>> > >> Zameer Manji
>> > >>
>> > >> <http://www.digitalprognosis.com>
>> >
>> >
>>
>
>

--001a11408a64dc69b40520768931--