You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by "Lu, Boying" <Bo...@emc.com> on 2016/08/18 09:56:58 UTC

A question to updatesstables

Hi, All,

We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is 'ic' format.
We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the
incompatible SSTable format and the log message told us to use 'nodetool updatesstables' to upgrade SSTable files.

To make sure that no negative impact on our data, I want to confirm following things about this command before trying it:

1.       Does it work without Cassandra server running?

2.       Will it cause data lost with this command?

3.       What's the best practice to void this error occurs again (e.g. upgrading Cassandra next time)?

Thanks

Boying

Re: A question to updatesstables

Posted by Romain Hardouin <ro...@yahoo.fr>.
Ok... you said 2.0.10 in the original post ;-)You can't upgrade from 1.2 to 2.1.2.0.7 is the minimum. So upgrade to 2.0.17 (the latest 2.0.X) first, see https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L244
Best,
Romain 

    Le Vendredi 19 août 2016 11h41, "Lu, Boying" <Bo...@emc.com> a écrit :
 

 #yiv4120164789 #yiv4120164789 -- _filtered #yiv4120164789 {font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv4120164789 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv4120164789 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv4120164789 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv4120164789 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv4120164789 {panose-1:2 1 6 0 3 1 1 1 1 1;}#yiv4120164789 #yiv4120164789 p.yiv4120164789MsoNormal, #yiv4120164789 li.yiv4120164789MsoNormal, #yiv4120164789 div.yiv4120164789MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv4120164789 a:link, #yiv4120164789 span.yiv4120164789MsoHyperlink {color:blue;text-decoration:underline;}#yiv4120164789 a:visited, #yiv4120164789 span.yiv4120164789MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv4120164789 p {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv4120164789 p.yiv4120164789MsoAcetate, #yiv4120164789 li.yiv4120164789MsoAcetate, #yiv4120164789 div.yiv4120164789MsoAcetate {margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv4120164789 p.yiv4120164789msoacetate, #yiv4120164789 li.yiv4120164789msoacetate, #yiv4120164789 div.yiv4120164789msoacetate {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv4120164789 p.yiv4120164789msonormal, #yiv4120164789 li.yiv4120164789msonormal, #yiv4120164789 div.yiv4120164789msonormal {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv4120164789 p.yiv4120164789msochpdefault, #yiv4120164789 li.yiv4120164789msochpdefault, #yiv4120164789 div.yiv4120164789msochpdefault {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv4120164789 span.yiv4120164789msohyperlink {}#yiv4120164789 span.yiv4120164789msohyperlinkfollowed {}#yiv4120164789 span.yiv4120164789emailstyle19 {}#yiv4120164789 span.yiv4120164789emailstyle20 {}#yiv4120164789 p.yiv4120164789msonormal1, #yiv4120164789 li.yiv4120164789msonormal1, #yiv4120164789 div.yiv4120164789msonormal1 {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv4120164789 span.yiv4120164789msohyperlink1 {color:blue;text-decoration:underline;}#yiv4120164789 span.yiv4120164789msohyperlinkfollowed1 {color:purple;text-decoration:underline;}#yiv4120164789 p.yiv4120164789msoacetate1, #yiv4120164789 li.yiv4120164789msoacetate1, #yiv4120164789 div.yiv4120164789msoacetate1 {margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv4120164789 span.yiv4120164789emailstyle191 {color:#1F497D;}#yiv4120164789 span.yiv4120164789emailstyle201 {color:#1F497D;}#yiv4120164789 p.yiv4120164789msochpdefault1, #yiv4120164789 li.yiv4120164789msochpdefault1, #yiv4120164789 div.yiv4120164789msochpdefault1 {margin-right:0cm;margin-left:0cm;font-size:10.0pt;}#yiv4120164789 span.yiv4120164789EmailStyle32 {color:#1F497D;}#yiv4120164789 span.yiv4120164789BalloonTextChar {}#yiv4120164789 .yiv4120164789MsoChpDefault {font-size:10.0pt;} _filtered #yiv4120164789 {margin:72.0pt 90.0pt 72.0pt 90.0pt;}#yiv4120164789 div.yiv4120164789WordSection1 {}#yiv4120164789 yes, we use Cassandra 2.1.11 in our latest release.    From: Romain Hardouin [mailto:romainh_ml@yahoo.fr]
Sent: 2016年8月19日 17:36
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables    ka is the 2.1 format... I don't understand. Did you install C* 2.1?    Romain    Le Vendredi 19 août 2016 11h32, "Lu, Boying" <Bo...@emc.com> a écrit :    Here is the error message in our log file: java.lang.RuntimeException: Incompatible SSTable found. Current version ka is unable to read file: /data/db/1/data/StorageOS/RemoteDirectorGroup/StorageOS-RemoteDirectorGroup-ic-37. Please run upgradesstables.     at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:517)     at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:494)     at org.apache.cassandra.db.Keyspace.initCf(Keyspace.java:335)     at org.apache.cassandra.db.Keyspace.<init>(Keyspace.java:275)     at org.apache.cassandra.db.Keyspace.open(Keyspace.java:121)     at org.apache.cassandra.db.Keyspace.open(Keyspace.java:98)     at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:328)     at org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:479)   From: Ryan Svihla [mailto:rs@foundev.pro]
Sent: 2016年8月19日 17:26
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables   The actual error message could be very useful to diagnose the reason. There are warnings about incompatible formats which are safe to ignore (usually in the cache) and I have one time seen an issue with commit log archiving preventing a startup during upgrade. Usually there is something else broken and the version mismatch is a false signal. 
Regards,   Ryan Svihla 
On Aug 18, 2016, at 10:18 PM, Lu, Boying <Bo...@emc.com> wrote: 
Thanks a lot.   I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running, and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?       From: Carlos Alonso [mailto:info@mrcalonso.com]
Sent: 2016年8月18日 18:44
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables   Replies inline 
 Carlos Alonso | Software Engineer | @calonso   On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com> wrote: Hi, All,   We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format. We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.   To make sure that no negative impact on our data, I want to confirm following things about this command before trying it: 1.      Does it work without Cassandra server running? No, it won't.  
2.      Will it cause data lost with this command? 
It shouldn't if you followed the upgrade instructions properly 
3.      What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)? 
Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it  
  Thanks   Boying 
  
  

RE: A question to updatesstables

Posted by "Lu, Boying" <Bo...@emc.com>.
yes, we use Cassandra 2.1.11 in our latest release.

From: Romain Hardouin [mailto:romainh_ml@yahoo.fr]
Sent: 2016年8月19日 17:36
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables

ka is the 2.1 format... I don't understand. Did you install C* 2.1?

Romain

Le Vendredi 19 août 2016 11h32, "Lu, Boying" <Bo...@emc.com>> a écrit :

Here is the error message in our log file:
java.lang.RuntimeException: Incompatible SSTable found. Current version ka is unable to read file: /data/db/1/data/StorageOS/RemoteDirectorGroup/StorageOS-RemoteDirectorGroup-ic-37. Please run upgradesstables.
    at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:517)
    at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:494)
    at org.apache.cassandra.db.Keyspace.initCf(Keyspace.java:335)
    at org.apache.cassandra.db.Keyspace.<init>(Keyspace.java:275)
    at org.apache.cassandra.db.Keyspace.open(Keyspace.java:121)
    at org.apache.cassandra.db.Keyspace.open(Keyspace.java:98)
    at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:328)
    at org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:479)

From: Ryan Svihla [mailto:rs@foundev.pro]
Sent: 2016年8月19日 17:26
To: user@cassandra.apache.org<ma...@cassandra.apache.org>
Subject: Re: A question to updatesstables

The actual error message could be very useful to diagnose the reason. There are warnings about incompatible formats which are safe to ignore (usually in the cache) and I have one time seen an issue with commit log archiving preventing a startup during upgrade. Usually there is something else broken and the version mismatch is a false signal.

Regards,

Ryan Svihla

On Aug 18, 2016, at 10:18 PM, Lu, Boying <Bo...@emc.com>> wrote:
Thanks a lot.

I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running,
and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?



From: Carlos Alonso [mailto:info@mrcalonso.com]
Sent: 2016年8月18日 18:44
To: user@cassandra.apache.org<ma...@cassandra.apache.org>
Subject: Re: A question to updatesstables

Replies inline

Carlos Alonso | Software Engineer | @calonso<https://twitter.com/calonso>

On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com>> wrote:
Hi, All,

We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format.
We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the
incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.

To make sure that no negative impact on our data, I want to confirm following things about this command before trying it:
1.       Does it work without Cassandra server running?
No, it won't.
2.       Will it cause data lost with this command?
It shouldn't if you followed the upgrade instructions properly
3.       What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)?
Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it

Thanks

Boying

Re: A question to updatesstables

Posted by Romain Hardouin <ro...@yahoo.fr>.
ka is the 2.1 format... I don't understand. Did you install C* 2.1?
Romain 

    Le Vendredi 19 août 2016 11h32, "Lu, Boying" <Bo...@emc.com> a écrit :
 

 #yiv1355196952 #yiv1355196952 -- _filtered #yiv1355196952 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv1355196952 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv1355196952 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv1355196952 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv1355196952 {panose-1:2 1 6 0 3 1 1 1 1 1;}#yiv1355196952 #yiv1355196952 p.yiv1355196952MsoNormal, #yiv1355196952 li.yiv1355196952MsoNormal, #yiv1355196952 div.yiv1355196952MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1355196952 a:link, #yiv1355196952 span.yiv1355196952MsoHyperlink {color:blue;text-decoration:underline;}#yiv1355196952 a:visited, #yiv1355196952 span.yiv1355196952MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv1355196952 p {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv1355196952 p.yiv1355196952MsoAcetate, #yiv1355196952 li.yiv1355196952MsoAcetate, #yiv1355196952 div.yiv1355196952MsoAcetate {margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv1355196952 span.yiv1355196952hoenzb {}#yiv1355196952 span.yiv1355196952EmailStyle19 {color:#1F497D;}#yiv1355196952 span.yiv1355196952EmailStyle20 {color:#1F497D;}#yiv1355196952 span.yiv1355196952BalloonTextChar {}#yiv1355196952 .yiv1355196952MsoChpDefault {font-size:10.0pt;} _filtered #yiv1355196952 {margin:72.0pt 90.0pt 72.0pt 90.0pt;}#yiv1355196952 div.yiv1355196952WordSection1 {}#yiv1355196952 Here is the error message in our log file: java.lang.RuntimeException: Incompatible SSTable found. Current version ka is unable to read file: /data/db/1/data/StorageOS/RemoteDirectorGroup/StorageOS-RemoteDirectorGroup-ic-37. Please run upgradesstables.     at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:517)     at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:494)     at org.apache.cassandra.db.Keyspace.initCf(Keyspace.java:335)     at org.apache.cassandra.db.Keyspace.<init>(Keyspace.java:275)     at org.apache.cassandra.db.Keyspace.open(Keyspace.java:121)     at org.apache.cassandra.db.Keyspace.open(Keyspace.java:98)     at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:328)     at org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:479)    From: Ryan Svihla [mailto:rs@foundev.pro]
Sent: 2016年8月19日 17:26
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables    The actual error message could be very useful to diagnose the reason. There are warnings about incompatible formats which are safe to ignore (usually in the cache) and I have one time seen an issue with commit log archiving preventing a startup during upgrade. Usually there is something else broken and the version mismatch is a false signal. 
Regards,    Ryan Svihla 
On Aug 18, 2016, at 10:18 PM, Lu, Boying <Bo...@emc.com> wrote: 
Thanks a lot.   I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running, and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?       From: Carlos Alonso [mailto:info@mrcalonso.com]
Sent: 2016年8月18日 18:44
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables   Replies inline 
 Carlos Alonso | Software Engineer | @calonso   On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com> wrote: Hi, All,   We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format. We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.   To make sure that no negative impact on our data, I want to confirm following things about this command before trying it: 1.      Does it work without Cassandra server running? No, it won't.  
2.      Will it cause data lost with this command? 
It shouldn't if you followed the upgrade instructions properly 
3.      What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)? 
Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it  
  Thanks   Boying 
 

RE: A question to updatesstables

Posted by "Lu, Boying" <Bo...@emc.com>.
Here is the error message in our log file:
java.lang.RuntimeException: Incompatible SSTable found. Current version ka is unable to read file: /data/db/1/data/StorageOS/RemoteDirectorGroup/StorageOS-RemoteDirectorGroup-ic-37. Please run upgradesstables.
    at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:517)
    at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:494)
    at org.apache.cassandra.db.Keyspace.initCf(Keyspace.java:335)
    at org.apache.cassandra.db.Keyspace.<init>(Keyspace.java:275)
    at org.apache.cassandra.db.Keyspace.open(Keyspace.java:121)
    at org.apache.cassandra.db.Keyspace.open(Keyspace.java:98)
    at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:328)
    at org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:479)

From: Ryan Svihla [mailto:rs@foundev.pro]
Sent: 2016年8月19日 17:26
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables

The actual error message could be very useful to diagnose the reason. There are warnings about incompatible formats which are safe to ignore (usually in the cache) and I have one time seen an issue with commit log archiving preventing a startup during upgrade. Usually there is something else broken and the version mismatch is a false signal.

Regards,

Ryan Svihla

On Aug 18, 2016, at 10:18 PM, Lu, Boying <Bo...@emc.com>> wrote:
Thanks a lot.

I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running,
and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?



From: Carlos Alonso [mailto:info@mrcalonso.com]
Sent: 2016年8月18日 18:44
To: user@cassandra.apache.org<ma...@cassandra.apache.org>
Subject: Re: A question to updatesstables

Replies inline

Carlos Alonso | Software Engineer | @calonso<https://twitter.com/calonso>

On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com>> wrote:
Hi, All,

We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format.
We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the
incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.

To make sure that no negative impact on our data, I want to confirm following things about this command before trying it:

1.       Does it work without Cassandra server running?
No, it won't.

2.       Will it cause data lost with this command?
It shouldn't if you followed the upgrade instructions properly

3.       What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)?
Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it

Thanks

Boying

Re: A question to updatesstables

Posted by Ryan Svihla <rs...@foundev.pro>.
The actual error message could be very useful to diagnose the reason. There are warnings about incompatible formats which are safe to ignore (usually in the cache) and I have one time seen an issue with commit log archiving preventing a startup during upgrade. Usually there is something else broken and the version mismatch is a false signal.

Regards,

Ryan Svihla

> On Aug 18, 2016, at 10:18 PM, Lu, Boying <Bo...@emc.com> wrote:
> 
> Thanks a lot.
>  
> I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running,
> and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?
>  
>  
>  
> From: Carlos Alonso [mailto:info@mrcalonso.com] 
> Sent: 2016年8月18日 18:44
> To: user@cassandra.apache.org
> Subject: Re: A question to updatesstables
>  
> Replies inline
> 
> Carlos Alonso | Software Engineer | @calonso
>  
> On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com> wrote:
> Hi, All,
>  
> We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format.
> We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the
> incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.
>  
> To make sure that no negative impact on our data, I want to confirm following things about this command before trying it:
> 1.       Does it work without Cassandra server running?
> 
> No, it won't. 
> 2.       Will it cause data lost with this command?
> 
> It shouldn't if you followed the upgrade instructions properly
> 3.       What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)?
> 
> Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it 
>  
> Thanks
>  
> Boying
>

Re: A question to updatesstables

Posted by Romain Hardouin <ro...@yahoo.fr>.
Hi,
There are two ways to upgrade SSTables: - online (C* must be UP): nodetool upgradesstables - offline (when C* is stopped): using the tool called "sstableupgrade".    It's located in the bin directory of Cassandra so depending on how you installed Cassandra, it may be on the path.    See https://docs.datastax.com/en/cassandra/2.0/cassandra/tools/ToolsSSTableupgrade_t.html
Few questions: - Did you check you are not hitting https://github.com/apache/cassandra/blob/cassandra-2.0/NEWS.txt#L162 ?    i.e. are you sure that all your data are in "ic" format? - Why did you choose 2.0.10? (The latest 2.0 release being 2.0.17.)  Best,  Romain 

    Le Vendredi 19 août 2016 5h18, "Lu, Boying" <Bo...@emc.com> a écrit :
 

 #yiv8524026874 #yiv8524026874 -- _filtered #yiv8524026874 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv8524026874 {font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv8524026874 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv8524026874 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv8524026874 {panose-1:2 1 6 0 3 1 1 1 1 1;}#yiv8524026874 #yiv8524026874 p.yiv8524026874MsoNormal, #yiv8524026874 li.yiv8524026874MsoNormal, #yiv8524026874 div.yiv8524026874MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv8524026874 a:link, #yiv8524026874 span.yiv8524026874MsoHyperlink {color:blue;text-decoration:underline;}#yiv8524026874 a:visited, #yiv8524026874 span.yiv8524026874MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv8524026874 p {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv8524026874 span.yiv8524026874hoenzb {}#yiv8524026874 span.yiv8524026874EmailStyle19 {color:#1F497D;}#yiv8524026874 .yiv8524026874MsoChpDefault {} _filtered #yiv8524026874 {margin:72.0pt 90.0pt 72.0pt 90.0pt;}#yiv8524026874 div.yiv8524026874WordSection1 {}#yiv8524026874 Thanks a lot.    I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running, and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?          From: Carlos Alonso [mailto:info@mrcalonso.com]
Sent: 2016年8月18日 18:44
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables    Replies inline 
 Carlos Alonso | Software Engineer | @calonso    On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com> wrote: Hi, All,   We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format. We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.   To make sure that no negative impact on our data, I want to confirm following things about this command before trying it: 1.      Does it work without Cassandra server running? No, it won't.  
2.      Will it cause data lost with this command? 
It shouldn't if you followed the upgrade instructions properly 
3.      What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)? 
Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it  
  Thanks   Boying 
  

RE: A question to updatesstables

Posted by "Lu, Boying" <Bo...@emc.com>.
Thanks a lot.

I’m a little bit of confusing.  If the ‘nodetool updatesstable’ doesn’t work without Cassandra server running,
and Cassandra server failed to start due to the incompatible SSTable format,  how to resolve this dilemma?



From: Carlos Alonso [mailto:info@mrcalonso.com]
Sent: 2016年8月18日 18:44
To: user@cassandra.apache.org
Subject: Re: A question to updatesstables

Replies inline

Carlos Alonso | Software Engineer | @calonso<https://twitter.com/calonso>

On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com>> wrote:
Hi, All,

We use Cassandra in our product. I our early release we use Cassandra 1.2.10 whose SSTable is ‘ic’ format.
We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra server failed to start due to the
incompatible SSTable format and the log message told us to use ‘nodetool updatesstables’ to upgrade SSTable files.

To make sure that no negative impact on our data, I want to confirm following things about this command before trying it:

1.       Does it work without Cassandra server running?
No, it won't.

2.       Will it cause data lost with this command?
It shouldn't if you followed the upgrade instructions properly

3.       What’s the best practice to void this error occurs again (e.g. upgrading Cassandra next time)?
Upgrading SSTables is required or not depending on the upgrade you're running, basically if the SSTables layout changes you'll need to run it and not otherwise so there's nothing you can do to avoid it

Thanks

Boying

Re: A question to updatesstables

Posted by Ryan Svihla <rs...@foundev.pro>.
It hasn't ever prevented me from starting unless there was something else
going on. Can you share the log message that's preventing you from starting.

On Thu, Aug 18, 2016, 5:44 AM Carlos Alonso <in...@mrcalonso.com> wrote:

> Replies inline
>
> Carlos Alonso | Software Engineer | @calonso <https://twitter.com/calonso>
>
> On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com> wrote:
>
>> Hi, All,
>>
>>
>>
>> We use Cassandra in our product. I our early release we use Cassandra
>> 1.2.10 whose SSTable is ‘ic’ format.
>>
>> We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra
>> server failed to start due to the
>>
>> incompatible SSTable format and the log message told us to use ‘nodetool
>> updatesstables’ to upgrade SSTable files.
>>
>>
>>
>> To make sure that no negative impact on our data, I want to confirm
>> following things about this command before trying it:
>>
>> 1.       Does it work without Cassandra server running?
>>
> No, it won't.
>
>> 2.       Will it cause data lost with this command?
>>
> It shouldn't if you followed the upgrade instructions properly
>
>> 3.       What’s the best practice to void this error occurs again (e.g.
>> upgrading Cassandra next time)?
>>
> Upgrading SSTables is required or not depending on the upgrade you're
> running, basically if the SSTables layout changes you'll need to run it and
> not otherwise so there's nothing you can do to avoid it
>
>>
>>
>> Thanks
>>
>>
>>
>> Boying
>>
>
> --
Regards,

Ryan Svihla

Re: A question to updatesstables

Posted by Carlos Alonso <in...@mrcalonso.com>.
Replies inline

Carlos Alonso | Software Engineer | @calonso <https://twitter.com/calonso>

On 18 August 2016 at 11:56, Lu, Boying <Bo...@emc.com> wrote:

> Hi, All,
>
>
>
> We use Cassandra in our product. I our early release we use Cassandra
> 1.2.10 whose SSTable is ‘ic’ format.
>
> We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra
> server failed to start due to the
>
> incompatible SSTable format and the log message told us to use ‘nodetool
> updatesstables’ to upgrade SSTable files.
>
>
>
> To make sure that no negative impact on our data, I want to confirm
> following things about this command before trying it:
>
> 1.       Does it work without Cassandra server running?
>
No, it won't.

> 2.       Will it cause data lost with this command?
>
It shouldn't if you followed the upgrade instructions properly

> 3.       What’s the best practice to void this error occurs again (e.g.
> upgrading Cassandra next time)?
>
Upgrading SSTables is required or not depending on the upgrade you're
running, basically if the SSTables layout changes you'll need to run it and
not otherwise so there's nothing you can do to avoid it

>
>
> Thanks
>
>
>
> Boying
>