CODEWITHSUNDEEP
cassandracassandra-3.0
baki
baki

Reputation: 39

After upgrade from Cassandra 3.0.8 to 3.0.14 do we have to run nodetool upgradesstables?

Recently we upgraded 8 cassandra nodes in 2 DC configuration from 3.0.8 to 3.0.14. So, should I have to run nodetool upgradesstables when upgrade 3.0.8 to 3.0.14?. If we should do it, what is the best practice to finish upgradesstables in a fastest way. Thanks.

Upvotes: 1

Views: 487

Answers (1)

Horia
Horia

Reputation: 2982

This is the comment from org.apache.cassandra.io.sstable.format.big.BigFormat

    // ma (3.0.0): swap bf hash order
    //             store rows natively
    // mb (3.0.7, 3.7): commit log lower bound included
    // mc (3.0.8, 3.9): commit log intervals included

    // na (4.0.0): uncompressed chunks, pending repair session
    //
    // NOTE: when adding a new version, please add that to LegacySSTableTest, too.

So, apparently, between 3.0.8 and 3.0.14 nothing new appeared regarding sstable versions.

But I did some testing using ccm and I found out that:

  • Cassandra 3.0.7 uses mb version for sstables.
  • Cassandra 3.0.8 uses mb version for sstables (still mb!!)
  • Cassandra 3.0.9 - 3.0.14 uses mc version for sstables.

Some other useful reading, although a bit outdated: one, two.

A way to check would be to go to your Cassandra data folder and check the sstable files to see which version they use. If different versions are in place, nodetool upgradesstables should be ran. I would run it one node at a time.

Upvotes: 0

Related Questions