“It takes as long as necessary to rewrite any sstable that needs to be upgraded”.
>From 2.2.4 to 2.2.6, the sstable format did not change, so there’s nothing to >upgrade. If you want to force the matter (and you probably don’t), ‘nodetool upgradesstables –a’ will rewrite them again, but you gain virtually nothing in the process. The version on disk will be a two letter sequence in the –Data.db file name – 2.0 uses –jb, 2.1 uses –ka, 2.2 uses –la, and so on. You should see files with –la in the name on 2.2.4 and 2.2.6. If a new format was added to 2.2, it would likely be –lb ( -l for 2.2, b for the second format ), and it would be documented at https://github.com/apache/cassandra/blob/cassandra-2.2/NEWS.txt - Jeff From: Kai Wang Reply-To: "user@cassandra.apache.org" Date: Saturday, June 4, 2016 at 9:36 AM To: "user@cassandra.apache.org" Subject: how long does "nodetool upgradesstables" take? I just upgrade C* from 2.2.4 to 2.2.6. I ran "nodetool upgradesstables" and it returned within a few seconds. Does this sound right? A few questions: 1. is it possible that sstable formats are the same between those versions that's why upgradesstables took almost no time? 2. is there a way to confirm the sstable version on disk? 3. is there a way to know if sstable format has changed from version to version? Thanks.
smime.p7s
Description: S/MIME cryptographic signature
