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.otterst...@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:jji...@gmail.com] 
> Sent: den 12 oktober 2017 23:11
> To: Cassandra DEV <dev@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...@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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to