You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Kevin Burton <bu...@spinn3r.com> on 2016/01/21 20:37:14 UTC

Strategy / order for upgradesstables during rolling upgrade.

I think there are two strategies to upgradesstables after a release.

We're doing a 2.0 to 2.1 upgrade (been procrastinating here).

I think we can go with B below... Would you agree?

Strategy A:

    - foreach server
        - upgrade to 2.1
        - nodetool upgradesstables

Strategy B:

    - foreach server
        - upgrade to 2.1
    - foreach server
        - nodetool upgradesstables


-- 

We’re hiring if you know of any awesome Java Devops or Linux Operations
Engineers!

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>

Re: Strategy / order for upgradesstables during rolling upgrade.

Posted by Jonathan Haddad <jo...@jonhaddad.com>.

Definitely B.

On Thu, Jan 21, 2016 at 11:42 AM Robert Coli <rc...@eventbrite.com> wrote:

> On Thu, Jan 21, 2016 at 11:37 AM, Kevin Burton <bu...@spinn3r.com> wrote:
>
>> I think there are two strategies to upgradesstables after a release.
>>
>> We're doing a 2.0 to 2.1 upgrade (been procrastinating here).
>>
>> I think we can go with B below... Would you agree?
>>
>> Strategy A:
>>
>>     - foreach server
>>         - upgrade to 2.1
>>         - nodetool upgradesstables
>>
>> Strategy B:
>>
>>     - foreach server
>>         - upgrade to 2.1
>>     - foreach server
>>         - nodetool upgradesstables
>>
>
> Yes, if you have the overall headroom, Strategy B will narrow the window
> where you are unable to do important streaming operations.
>
> =Rob
>
>

Re: Strategy / order for upgradesstables during rolling upgrade.

Posted by Robert Coli <rc...@eventbrite.com>.

On Thu, Jan 21, 2016 at 11:37 AM, Kevin Burton <bu...@spinn3r.com> wrote:

> I think there are two strategies to upgradesstables after a release.
>
> We're doing a 2.0 to 2.1 upgrade (been procrastinating here).
>
> I think we can go with B below... Would you agree?
>
> Strategy A:
>
>     - foreach server
>         - upgrade to 2.1
>         - nodetool upgradesstables
>
> Strategy B:
>
>     - foreach server
>         - upgrade to 2.1
>     - foreach server
>         - nodetool upgradesstables
>

Yes, if you have the overall headroom, Strategy B will narrow the window
where you are unable to do important streaming operations.

=Rob