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

Posted to dev@cassandra.apache.org by "Li, Guangxing" <gu...@pearson.com> on 2017/10/12 20:59:26 UTC

Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Hi,

I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did not
run 'nodetool upgradesstables' at all. Per my confirmation afterwards,
everything is fine. But according to documentation at
https://support.datastax.com/hc/en-us/articles/208040036-Nodetool-upgradesstables-FAQ.
I need to do that.
So can someone tell me if I must do 'nodetool upgradesstables' after
upgrading each node from 2.0.9 to 2.1.19?

Thanks.

George.

Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by Marcus Eriksson <kr...@gmail.com>.

https://issues.apache.org/jira/browse/CASSANDRA-10990

On Fri, Oct 13, 2017 at 9:00 AM, Per Otterström <per.otterstrom@ericsson.com
> wrote:

> Hepp!
>
> Just to be clear, I'm not claiming this to be the case, it is a sincere
> question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm
> asking. Some initial tests indicate that repairs etc work well before
> running upgradesstables (assuming all nodes are upgraded to 3.0). But if
> there are known corner cases I'd be interested to know.
>
> We need to support reading old sstables in order to support rolling
> upgrades. This seem to be a general assumption that people agree on. I'm
> not sure there is a clear agreement on the streaming part. Would it make
> sense to clarify this in documentation?
>
> /pelle
>
> -----Original Message-----
> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> Sent: den 13 oktober 2017 08:09
> To: dev@cassandra.apache.org
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating
> from 2.0.9 to 2.1.19?
>
> Two people say I’m wrong, I’ll believe it - must be imagining restrictions
> that don’t exist.
>
> --
> Jeff Jirsa
>
>
> > On Oct 12, 2017, at 10:55 PM, Per Otterström <
> per.otterstrom@ericsson.com> wrote:
> >
> > Hi!
> >
> > This was news to me. I had the impression that we are maintaining
> backwards compatibility for streaming non-upgraded sstables. Is that not
> the case?
> >
> > However, I believe it is a good idea to run upgradesstables at some
> point _before_ upgrading Cassandra next time to make sure there are no old
> sstables around before you take the next step.
> >
> > /pelle
> >
> > -----Original Message-----
> > From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> > Sent: den 12 oktober 2017 23:11
> > To: Cassandra DEV <de...@cassandra.apache.org>
> > Subject: Re: Do it need to run 'nodetool upgradesstables' when updating
> from 2.0.9 to 2.1.19?
> >
> > You won't notice any issues (all versions of cassandra are backwards
> compatible at least 1 version), and sstables will be slowly migrated to the
> new format as you compact, but you should still run it (upgradesstables)
> explicitly because when it comes time to run repair/boostrap/decommission/etc,
> you'll need all sstables on the same/current format.
> >
> >
> >
> > On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <guangxing.li@pearson.com
> >
> > wrote:
> >
> >> Hi,
> >>
> >> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did
> >> not run 'nodetool upgradesstables' at all. Per my confirmation
> >> afterwards, everything is fine. But according to documentation at
> >> https://support.datastax.com/hc/en-us/articles/208040036-
> >> Nodetool-upgradesstables-FAQ.
> >> I need to do that.
> >> So can someone tell me if I must do 'nodetool upgradesstables' after
> >> upgrading each node from 2.0.9 to 2.1.19?
> >>
> >> Thanks.
> >>
> >> George.
> >>
> >  B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•
> È [œÝXœØÜšX™K  K[XZ[
> ˆ  ]‹][œÝXœØÜšX™P Ø\ÜØ[™ ˜K˜\ XÚ K›Ü™ÃB‘›Üˆ Y  ] [Û˜[  ÛÛ[X[™ Ë  K[XZ[
> ˆ  ]‹Z [   Ø\ÜØ[™ ˜K˜\ XÚ K›Ü™ÃBƒB
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>

Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

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

After an upgrade I recommend running upgrade sstables no matter what the
version change is. If it's not needed, nothing will happen.
On Fri, Oct 13, 2017 at 4:30 AM Steinmaurer, Thomas <
thomas.steinmaurer@dynatrace.com> wrote:

> And extremely useful/important in the field not being a strict requirement
> immediately upgrading sstables, especially for not closely monitored
> environments, e.g. unattended deployments like development machines or even
> customer on-prem installations etc.
>
> Cassandra's data backwards compatibility is one of the best I have seen.
>
> Thanks a lot for that!
>
> T.
>
>
> -----Original Message-----
> From: J. D. Jordan [mailto:jeremiah.jordan@gmail.com]
> Sent: Freitag, 13. Oktober 2017 13:13
> To: dev@cassandra.apache.org
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating
> from 2.0.9 to 2.1.19?
>
> Old restrictions that have been lifted Jeff :) Ever since 2.0 we have
> supported streaming old sstables, see here for the 2.0 ticket:
> https://issues.apache.org/jira/browse/CASSANDRA-5772
>
> That was broken in early 3.0, but had since been fixed by the ticket
> Marcus linked https://issues.apache.org/jira/browse/CASSANDRA-10990
>
> So it should be fine in all latest 3.x versions.
>
> -Jeremiah
>
>
> > On Oct 13, 2017, at 3:34 AM, Steinmaurer, Thomas <
> thomas.steinmaurer@dynatrace.com> wrote:
> >
> > Same here, regarding sincere question to know the corner cases from 2.1
> => 3.11.1, but Marcus already provided the JIRA ticket.
> >
> > Thanks!
> >
> >
> > -----Original Message-----
> > From: Per OtterstrÃ¶m [mailto:per.otterstrom@ericsson.com]
> > Sent: Freitag, 13. Oktober 2017 09:01
> > To: dev@cassandra.apache.org
> > Subject: RE: Do it need to run 'nodetool upgradesstables' when updating
> from 2.0.9 to 2.1.19?
> >
> > Hepp!
> >
> > Just to be clear, I'm not claiming this to be the case, it is a sincere
> question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm
> asking. Some initial tests indicate that repairs etc work well before
> running upgradesstables (assuming all nodes are upgraded to 3.0). But if
> there are known corner cases I'd be interested to know.
> >
> > We need to support reading old sstables in order to support rolling
> upgrades. This seem to be a general assumption that people agree on. I'm
> not sure there is a clear agreement on the streaming part. Would it make
> sense to clarify this in documentation?
> >
> > /pelle
> >
> > -----Original Message-----
> > From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> > Sent: den 13 oktober 2017 08:09
> > To: dev@cassandra.apache.org
> > Subject: Re: Do it need to run 'nodetool upgradesstables' when updating
> from 2.0.9 to 2.1.19?
> >
> > Two people say Iâ€™m wrong, Iâ€™ll believe it - must be imagining
> restrictions that donâ€™t exist.
> >
> > --
> > Jeff Jirsa
> >
> >
> >> On Oct 12, 2017, at 10:55 PM, Per OtterstrÃ¶m <
> per.otterstrom@ericsson.com> wrote:
> >>
> >> Hi!
> >>
> >> This was news to me. I had the impression that we are maintaining
> backwards compatibility for streaming non-upgraded sstables. Is that not
> the case?
> >>
> >> However, I believe it is a good idea to run upgradesstables at some
> point _before_ upgrading Cassandra next time to make sure there are no old
> sstables around before you take the next step.
> >>
> >> /pelle
> >>
> >> -----Original Message-----
> >> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> >> Sent: den 12 oktober 2017 23:11
> >> To: Cassandra DEV <de...@cassandra.apache.org>
> >> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating
> from 2.0.9 to 2.1.19?
> >>
> >> You won't notice any issues (all versions of cassandra are backwards
> compatible at least 1 version), and sstables will be slowly migrated to the
> new format as you compact, but you should still run it (upgradesstables)
> explicitly because when it comes time to run
> repair/boostrap/decommission/etc, you'll need all sstables on the
> same/current format.
> >>
> >>
> >>
> >> On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing
> >> <gu...@pearson.com>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I
> >>> did not run 'nodetool upgradesstables' at all. Per my confirmation
> >>> afterwards, everything is fine. But according to documentation at
> >>> https://support.datastax.com/hc/en-us/articles/208040036-
> >>> Nodetool-upgradesstables-FAQ.
> >>> I need to do that.
> >>> So can someone tell me if I must do 'nodetool upgradesstables' after
> >>> upgrading each node from 2.0.9 to 2.1.19?
> >>>
> >>> Thanks.
> >>>
> >>> George.
> >>>
> >>  Bâ€¹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> >> KKKKCBâ€¢ Ãˆ [Å“Ã XÅ“Ã˜ÃœÅ¡Xâ„¢K  K[XZ[
> > Ë†  ]â€¹][Å“Ã XÅ“Ã˜ÃœÅ¡Xâ„¢P Ã˜\ÃœÃ˜[â„¢ ËœKËœ\ XÃš Kâ€ºÃœâ„¢ÃƒBâ€˜â€º
> > ÃœË† Y  ] [Ã›Ëœ[  Ã›Ã›[X[â„¢ Ã‹  K[XZ[
> > Ë†  ]â€¹Z [   Ã˜\ÃœÃ˜[â„¢ ËœKËœ\ XÃš Kâ€ºÃœâ„¢ÃƒBÆ’B
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >  Bï¿½KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> > KKKCBï¿½ ï¿½ [ï¿½ï¿½Xï¿½ï¿½ÜšXï¿½K  K[XZ[
> > ï¿½  ]ï¿½][ï¿½ï¿½Xï¿½ï¿½ÜšXï¿½P ï¿½\ï¿½ï¿½[ï¿½ ï¿½Kï¿½\ Xï¿½ Kï¿½Ü™ï¿½
> > Bï¿½ï¿½Üˆ Y  ] [Û˜[  ï¿½ï¿½[X[ï¿½ ï¿½  K[XZ[
> > ï¿½  ]ï¿½Z [   ï¿½\ï¿½ï¿½[ï¿½ ï¿½Kï¿½\ Xï¿½ Kï¿½Ü™ï¿½Bï¿½B
> > The contents of this e-mail are intended for the named addressee only.
> > It contains information that may be confidential. Unless you are the
> > named addressee or an authorized designee, you may not copy or use it,
> > or disclose it to anyone else. If you received it in error please
> > notify us immediately and then destroy it. Dynatrace Austria GmbH
> > (registration number FN 91482h) is a company registered in Linz whose
> > registered office is at 4040 Linz, Austria, FreistÃ¤dterstraÃŸe 313
> >  B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> > KCB• È [œÝXœØÜšX™K  K[XZ[
> ˆ  ]‹][œÝXœØÜšX™P Ø\ÜØ[™ ˜K˜\ XÚ K›Ü™ÃB‘›Üˆ
> > Y  ] [Û˜[  ÛÛ[X[™ Ë  K[XZ[
> ˆ  ]‹Z [   Ø\ÜØ[™ ˜K˜\ XÚ K›Ü™ÃBƒB
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
> disclose it to anyone else. If you received it in error please notify us
> immediately and
> <https://maps.google.com/?q=in+error+please+notify+us+immediately+and&entry=gmail&source=g>then
> destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a
> company registered in Linz whose registered office is at 4040 Linz,
> Austria, Freistädterstraße 313
>

RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by "Steinmaurer, Thomas" <th...@dynatrace.com>.

And extremely useful/important in the field not being a strict requirement immediately upgrading sstables, especially for not closely monitored environments, e.g. unattended deployments like development machines or even customer on-prem installations etc.

Cassandra's data backwards compatibility is one of the best I have seen.

Thanks a lot for that!

T.


-----Original Message-----
From: J. D. Jordan [mailto:jeremiah.jordan@gmail.com]
Sent: Freitag, 13. Oktober 2017 13:13
To: dev@cassandra.apache.org
Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Old restrictions that have been lifted Jeff :) Ever since 2.0 we have supported streaming old sstables, see here for the 2.0 ticket:
https://issues.apache.org/jira/browse/CASSANDRA-5772

That was broken in early 3.0, but had since been fixed by the ticket Marcus linked https://issues.apache.org/jira/browse/CASSANDRA-10990

So it should be fine in all latest 3.x versions.

-Jeremiah


> On Oct 13, 2017, at 3:34 AM, Steinmaurer, Thomas <th...@dynatrace.com> wrote:
>
> Same here, regarding sincere question to know the corner cases from 2.1 => 3.11.1, but Marcus already provided the JIRA ticket.
>
> Thanks!
>
>
> -----Original Message-----
> From: Per OtterstrÃ¶m [mailto:per.otterstrom@ericsson.com]
> Sent: Freitag, 13. Oktober 2017 09:01
> To: dev@cassandra.apache.org
> Subject: RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
>
> Hepp!
>
> Just to be clear, I'm not claiming this to be the case, it is a sincere question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm asking. Some initial tests indicate that repairs etc work well before running upgradesstables (assuming all nodes are upgraded to 3.0). But if there are known corner cases I'd be interested to know.
>
> We need to support reading old sstables in order to support rolling upgrades. This seem to be a general assumption that people agree on. I'm not sure there is a clear agreement on the streaming part. Would it make sense to clarify this in documentation?
>
> /pelle
>
> -----Original Message-----
> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> Sent: den 13 oktober 2017 08:09
> To: dev@cassandra.apache.org
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
>
> Two people say Iâ€™m wrong, Iâ€™ll believe it - must be imagining restrictions that donâ€™t exist.
>
> --
> Jeff Jirsa
>
>
>> On Oct 12, 2017, at 10:55 PM, Per OtterstrÃ¶m <pe...@ericsson.com> wrote:
>>
>> Hi!
>>
>> This was news to me. I had the impression that we are maintaining backwards compatibility for streaming non-upgraded sstables. Is that not the case?
>>
>> However, I believe it is a good idea to run upgradesstables at some point _before_ upgrading Cassandra next time to make sure there are no old sstables around before you take the next step.
>>
>> /pelle
>>
>> -----Original Message-----
>> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
>> Sent: den 12 oktober 2017 23:11
>> To: Cassandra DEV <de...@cassandra.apache.org>
>> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
>>
>> You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.
>>
>>
>>
>> On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing
>> <gu...@pearson.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I
>>> did not run 'nodetool upgradesstables' at all. Per my confirmation
>>> afterwards, everything is fine. But according to documentation at
>>> https://support.datastax.com/hc/en-us/articles/208040036-
>>> Nodetool-upgradesstables-FAQ.
>>> I need to do that.
>>> So can someone tell me if I must do 'nodetool upgradesstables' after
>>> upgrading each node from 2.0.9 to 2.1.19?
>>>
>>> Thanks.
>>>
>>> George.
>>>
>> Bâ€¹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
>> KKKKCBâ€¢Ãˆ[Å“ÃXÅ“Ã˜ÃœÅ¡Xâ„¢KK[XZ[
> Ë†]â€¹][Å“ÃXÅ“Ã˜ÃœÅ¡Xâ„¢PÃ˜\ÃœÃ˜[â„¢ËœKËœ\XÃšKâ€ºÃœâ„¢ÃƒBâ€˜â€º
> ÃœË†Y][Ã›Ëœ[Ã›Ã›[X[â„¢Ã‹K[XZ[
> Ë†]â€¹Z[Ã˜\ÃœÃ˜[â„¢ËœKËœ\XÃšKâ€ºÃœâ„¢ÃƒBÆ’B
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
> Bï¿½KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> KKKCBï¿½ï¿½[ï¿½ï¿½Xï¿½ï¿½ÜšXï¿½KK[XZ[
> ï¿½]ï¿½][ï¿½ï¿½Xï¿½ï¿½ÜšXï¿½Pï¿½\ï¿½ï¿½[ï¿½ï¿½Kï¿½\Xï¿½Kï¿½Ü™ï¿½
> Bï¿½ï¿½ÜˆY][Û˜[ï¿½ï¿½[X[ï¿½ï¿½K[XZ[
> ï¿½]ï¿½Z[ï¿½\ï¿½ï¿½[ï¿½ï¿½Kï¿½\Xï¿½Kï¿½Ü™ï¿½Bï¿½B
> The contents of this e-mail are intended for the named addressee only.
> It contains information that may be confidential. Unless you are the
> named addressee or an authorized designee, you may not copy or use it,
> or disclose it to anyone else. If you received it in error please
> notify us immediately and then destroy it. Dynatrace Austria GmbH
> (registration number FN 91482h) is a company registered in Linz whose
> registered office is at 4040 Linz, Austria, FreistÃ¤dterstraÃŸe 313
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
> KCB•È[œÝXœØÜšX™KK[XZ[
ˆ]‹][œÝXœØÜšX™PØ\ÜØ[™˜K˜\XÚK›Ü™ÃB‘›Üˆ
> Y][Û˜[ÛÛ[X[™ËK[XZ[
ˆ]‹Z[Ø\ÜØ[™˜K˜\XÚK›Ü™ÃBƒB
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freistädterstraße 313

Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by "J. D. Jordan" <je...@gmail.com>.

Old restrictions that have been lifted Jeff :)
Ever since 2.0 we have supported streaming old sstables, see here for the 2.0 ticket:
https://issues.apache.org/jira/browse/CASSANDRA-5772

That was broken in early 3.0, but had since been fixed by the ticket Marcus linked https://issues.apache.org/jira/browse/CASSANDRA-10990

So it should be fine in all latest 3.x versions.

-Jeremiah


> On Oct 13, 2017, at 3:34 AM, Steinmaurer, Thomas <th...@dynatrace.com> wrote:
> 
> Same here, regarding sincere question to know the corner cases from 2.1 => 3.11.1, but Marcus already provided the JIRA ticket.
> 
> Thanks!
> 
> 
> -----Original Message-----
> From: Per OtterstrÃ¶m [mailto:per.otterstrom@ericsson.com]
> Sent: Freitag, 13. Oktober 2017 09:01
> To: dev@cassandra.apache.org
> Subject: RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
> 
> Hepp!
> 
> Just to be clear, I'm not claiming this to be the case, it is a sincere question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm asking. Some initial tests indicate that repairs etc work well before running upgradesstables (assuming all nodes are upgraded to 3.0). But if there are known corner cases I'd be interested to know.
> 
> We need to support reading old sstables in order to support rolling upgrades. This seem to be a general assumption that people agree on. I'm not sure there is a clear agreement on the streaming part. Would it make sense to clarify this in documentation?
> 
> /pelle
> 
> -----Original Message-----
> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> Sent: den 13 oktober 2017 08:09
> To: dev@cassandra.apache.org
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
> 
> Two people say Iâ€™m wrong, Iâ€™ll believe it - must be imagining restrictions that donâ€™t exist.
> 
> --
> Jeff Jirsa
> 
> 
>> On Oct 12, 2017, at 10:55 PM, Per OtterstrÃ¶m <pe...@ericsson.com> wrote:
>> 
>> Hi!
>> 
>> This was news to me. I had the impression that we are maintaining backwards compatibility for streaming non-upgraded sstables. Is that not the case?
>> 
>> However, I believe it is a good idea to run upgradesstables at some point _before_ upgrading Cassandra next time to make sure there are no old sstables around before you take the next step.
>> 
>> /pelle
>> 
>> -----Original Message-----
>> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
>> Sent: den 12 oktober 2017 23:11
>> To: Cassandra DEV <de...@cassandra.apache.org>
>> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
>> 
>> You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.
>> 
>> 
>> 
>> On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
>> wrote:
>> 
>>> Hi,
>>> 
>>> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did
>>> not run 'nodetool upgradesstables' at all. Per my confirmation
>>> afterwards, everything is fine. But according to documentation at
>>> https://support.datastax.com/hc/en-us/articles/208040036-
>>> Nodetool-upgradesstables-FAQ.
>>> I need to do that.
>>> So can someone tell me if I must do 'nodetool upgradesstables' after
>>> upgrading each node from 2.0.9 to 2.1.19?
>>> 
>>> Thanks.
>>> 
>>> George.
>>> 
>> Bâ€¹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCBâ€¢Ãˆ[Å“ÃXÅ“Ã˜ÃœÅ¡Xâ„¢KK[XZ[
> Ë†]â€¹][Å“ÃXÅ“Ã˜ÃœÅ¡Xâ„¢PÃ˜\ÃœÃ˜[â„¢ËœKËœ\XÃšKâ€ºÃœâ„¢ÃƒBâ€˜â€ºÃœË†Y][Ã›Ëœ[Ã›Ã›[X[â„¢Ã‹K[XZ[
> Ë†]â€¹Z[Ã˜\ÃœÃ˜[â„¢ËœKËœ\XÃšKâ€ºÃœâ„¢ÃƒBÆ’B
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
> 
> Bï¿½KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCBï¿½ï¿½[ï¿½ï¿½Xï¿½ï¿½ÜšXï¿½KK[XZ[
> ï¿½]ï¿½][ï¿½ï¿½Xï¿½ï¿½ÜšXï¿½Pï¿½\ï¿½ï¿½[ï¿½ï¿½Kï¿½\Xï¿½Kï¿½Ü™ï¿½Bï¿½ï¿½ÜˆY][Û˜[ï¿½ï¿½[X[ï¿½ï¿½K[XZ[
> ï¿½]ï¿½Z[ï¿½\ï¿½ï¿½[ï¿½ï¿½Kï¿½\Xï¿½Kï¿½Ü™ï¿½Bï¿½B
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, FreistÃ¤dterstraÃŸe 313
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•È[œÝXœØÜšX™KK[XZ[ˆ]‹][œÝXœØÜšX™PØ\ÜØ[™˜K˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ËK[XZ[ˆ]‹Z[Ø\ÜØ[™˜K˜\XÚK›Ü™ÃBƒB

RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by "Steinmaurer, Thomas" <th...@dynatrace.com>.

Same here, regarding sincere question to know the corner cases from 2.1 => 3.11.1, but Marcus already provided the JIRA ticket.

Thanks!

-----Original Message-----
From: Per Otterström [mailto:per.otterstrom@ericsson.com]
Sent: Freitag, 13. Oktober 2017 09:01
To: dev@cassandra.apache.org
Subject: RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Hepp!

Just to be clear, I'm not claiming this to be the case, it is a sincere question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm asking. Some initial tests indicate that repairs etc work well before running upgradesstables (assuming all nodes are upgraded to 3.0). But if there are known corner cases I'd be interested to know.

We need to support reading old sstables in order to support rolling upgrades. This seem to be a general assumption that people agree on. I'm not sure there is a clear agreement on the streaming part. Would it make sense to clarify this in documentation?

/pelle

-----Original Message-----
From: Jeff Jirsa [mailto:jjirsa@gmail.com]
Sent: den 13 oktober 2017 08:09
To: dev@cassandra.apache.org
Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Two people say I’m wrong, I’ll believe it - must be imagining restrictions that don’t exist.

--
Jeff Jirsa

> On Oct 12, 2017, at 10:55 PM, Per Otterström <pe...@ericsson.com> wrote:
>
> Hi!
>
> This was news to me. I had the impression that we are maintaining backwards compatibility for streaming non-upgraded sstables. Is that not the case?
>
> However, I believe it is a good idea to run upgradesstables at some point _before_ upgrading Cassandra next time to make sure there are no old sstables around before you take the next step.
>
> /pelle
>
> -----Original Message-----
> From: Jeff Jirsa [mailto:jjirsa@gmail.com]
> Sent: den 12 oktober 2017 23:11
> To: Cassandra DEV <de...@cassandra.apache.org>
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
>
> You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.
>
>
>
> On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
> wrote:
>
>> Hi,
>>
>> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did
>> not run 'nodetool upgradesstables' at all. Per my confirmation
>> afterwards, everything is fine. But according to documentation at
>> https://support.datastax.com/hc/en-us/articles/208040036-
>> Nodetool-upgradesstables-FAQ.
>> I need to do that.
>> So can someone tell me if I must do 'nodetool upgradesstables' after
>> upgrading each node from 2.0.9 to 2.1.19?
>>
>> Thanks.
>>
>> George.
>>
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•È[œÝXœØÜšX™KK[XZ[
ˆ]‹][œÝXœØÜšX™PØ\ÜØ[™˜K˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ËK[XZ[
ˆ]‹Z[Ø\ÜØ[™˜K˜\XÚK›Ü™ÃBƒB

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org

B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB��[��X��ܚX�KK[XZ[
�]�][��X��ܚX�P�\��[��K�\X�K�ܙ�B��܈Y][ۘ[��[X[��K[XZ[
�]�Z[�\��[��K�\X�K�ܙ�B�B
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freistädterstraße 313

RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by Per Otterström <pe...@ericsson.com>.

Hepp!

Just to be clear, I'm not claiming this to be the case, it is a sincere question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm asking. Some initial tests indicate that repairs etc work well before running upgradesstables (assuming all nodes are upgraded to 3.0). But if there are known corner cases I'd be interested to know.

We need to support reading old sstables in order to support rolling upgrades. This seem to be a general assumption that people agree on. I'm not sure there is a clear agreement on the streaming part. Would it make sense to clarify this in documentation?

/pelle

-----Original Message-----
From: Jeff Jirsa [mailto:jjirsa@gmail.com] 
Sent: den 13 oktober 2017 08:09
To: dev@cassandra.apache.org
Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Two people say I’m wrong, I’ll believe it - must be imagining restrictions that don’t exist.

-- 
Jeff Jirsa


> On Oct 12, 2017, at 10:55 PM, Per Otterström <pe...@ericsson.com> wrote:
> 
> Hi!
> 
> This was news to me. I had the impression that we are maintaining backwards compatibility for streaming non-upgraded sstables. Is that not the case?
> 
> However, I believe it is a good idea to run upgradesstables at some point _before_ upgrading Cassandra next time to make sure there are no old sstables around before you take the next step.
> 
> /pelle
> 
> -----Original Message-----
> From: Jeff Jirsa [mailto:jjirsa@gmail.com] 
> Sent: den 12 oktober 2017 23:11
> To: Cassandra DEV <de...@cassandra.apache.org>
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
> 
> You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.
> 
> 
> 
> On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
> wrote:
> 
>> Hi,
>> 
>> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did 
>> not run 'nodetool upgradesstables' at all. Per my confirmation 
>> afterwards, everything is fine. But according to documentation at
>> https://support.datastax.com/hc/en-us/articles/208040036-
>> Nodetool-upgradesstables-FAQ.
>> I need to do that.
>> So can someone tell me if I must do 'nodetool upgradesstables' after 
>> upgrading each node from 2.0.9 to 2.1.19?
>> 
>> Thanks.
>> 
>> George.
>> 
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•È[œÝXœØÜšX™KK[XZ[
ˆ]‹][œÝXœØÜšX™PØ\ÜØ[™˜K˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ËK[XZ[
ˆ]‹Z[Ø\ÜØ[™˜K˜\XÚK›Ü™ÃBƒB

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org

Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by Jeff Jirsa <jj...@gmail.com>.

Two people say I’m wrong, I’ll believe it - must be imagining restrictions that don’t exist.

-- 
Jeff Jirsa


> On Oct 12, 2017, at 10:55 PM, Per Otterström <pe...@ericsson.com> wrote:
> 
> Hi!
> 
> This was news to me. I had the impression that we are maintaining backwards compatibility for streaming non-upgraded sstables. Is that not the case?
> 
> However, I believe it is a good idea to run upgradesstables at some point _before_ upgrading Cassandra next time to make sure there are no old sstables around before you take the next step.
> 
> /pelle
> 
> -----Original Message-----
> From: Jeff Jirsa [mailto:jjirsa@gmail.com] 
> Sent: den 12 oktober 2017 23:11
> To: Cassandra DEV <de...@cassandra.apache.org>
> Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?
> 
> You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.
> 
> 
> 
> On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
> wrote:
> 
>> Hi,
>> 
>> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did 
>> not run 'nodetool upgradesstables' at all. Per my confirmation 
>> afterwards, everything is fine. But according to documentation at
>> https://support.datastax.com/hc/en-us/articles/208040036-
>> Nodetool-upgradesstables-FAQ.
>> I need to do that.
>> So can someone tell me if I must do 'nodetool upgradesstables' after 
>> upgrading each node from 2.0.9 to 2.1.19?
>> 
>> Thanks.
>> 
>> George.
>> 
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•È[œÝXœØÜšX™KK[XZ[ˆ]‹][œÝXœØÜšX™PØ\ÜØ[™˜K˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ËK[XZ[ˆ]‹Z[Ø\ÜØ[™˜K˜\XÚK›Ü™ÃBƒB

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org

RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by Per Otterström <pe...@ericsson.com>.

Hi!

This was news to me. I had the impression that we are maintaining backwards compatibility for streaming non-upgraded sstables. Is that not the case?

However, I believe it is a good idea to run upgradesstables at some point _before_ upgrading Cassandra next time to make sure there are no old sstables around before you take the next step.

/pelle

-----Original Message-----
From: Jeff Jirsa [mailto:jjirsa@gmail.com] 
Sent: den 12 oktober 2017 23:11
To: Cassandra DEV <de...@cassandra.apache.org>
Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.

On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
wrote:

> Hi,
>
> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did 
> not run 'nodetool upgradesstables' at all. Per my confirmation 
> afterwards, everything is fine. But according to documentation at
> https://support.datastax.com/hc/en-us/articles/208040036-
> Nodetool-upgradesstables-FAQ.
> I need to do that.
> So can someone tell me if I must do 'nodetool upgradesstables' after 
> upgrading each node from 2.0.9 to 2.1.19?
>
> Thanks.
>
> George.
>

RE: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by "Steinmaurer, Thomas" <th...@dynatrace.com>.

Hi Jeff,

I was under the impression that streaming in a cluster with mixed binary versions might be problematic, but as long as the cluster is on the same binary version (e.g. after a rolling upgrade), we still can have SStables in mixed data formats and streaming will work?

Thanks,
Thomas

-----Original Message-----
From: Jeff Jirsa [mailto:jjirsa@gmail.com]
Sent: Donnerstag, 12. Oktober 2017 23:11
To: Cassandra DEV <de...@cassandra.apache.org>
Subject: Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

You won't notice any issues (all versions of cassandra are backwards compatible at least 1 version), and sstables will be slowly migrated to the new format as you compact, but you should still run it (upgradesstables) explicitly because when it comes time to run repair/boostrap/decommission/etc, you'll need all sstables on the same/current format.

On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
wrote:

> Hi,
>
> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did
> not run 'nodetool upgradesstables' at all. Per my confirmation
> afterwards, everything is fine. But according to documentation at
> https://support.datastax.com/hc/en-us/articles/208040036-
> Nodetool-upgradesstables-FAQ.
> I need to do that.
> So can someone tell me if I must do 'nodetool upgradesstables' after
> upgrading each node from 2.0.9 to 2.1.19?
>
> Thanks.
>
> George.
>
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freistädterstraße 313

Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Posted by Jeff Jirsa <jj...@gmail.com>.

You won't notice any issues (all versions of cassandra are backwards
compatible at least 1 version), and sstables will be slowly migrated to the
new format as you compact, but you should still run it (upgradesstables)
explicitly because when it comes time to run
repair/boostrap/decommission/etc, you'll need all sstables on the
same/current format.

On Thu, Oct 12, 2017 at 1:59 PM, Li, Guangxing <gu...@pearson.com>
wrote:

> Hi,
>
> I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did not
> run 'nodetool upgradesstables' at all. Per my confirmation afterwards,
> everything is fine. But according to documentation at
> https://support.datastax.com/hc/en-us/articles/208040036-
> Nodetool-upgradesstables-FAQ.
> I need to do that.
> So can someone tell me if I must do 'nodetool upgradesstables' after
> upgrading each node from 2.0.9 to 2.1.19?
>
> Thanks.
>
> George.
>