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" <boying...@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:r...@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 <boying...@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:i...@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 <boying...@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
