There's no harm in running it during any upgrade, and I always recommend doing it just to be in the habit.
My 2 cents. On Wed, Apr 25, 2018 at 3:39 PM Christophe Schmitz < christo...@instaclustr.com> wrote: > Hi Pranay, > > You only need to upgrade your SSTables when you perform a major Cassandra > version upgrade, so you don't need to run it for upgrading in the 3.x.x > series. > One way to check which storage version your SSTables are using is to look > at the SSTables name. It is structured as: > <version>-<generation>-<component>.db The version is a string that > represents the SSTable storage format version. > The version is "mc" in the 3.x.x series. > > Cheers, > Christophe > > > > On 26 April 2018 at 06:06, Pranay akula <pranay.akula2...@gmail.com> > wrote: > >> When is it necessary to upgrade SSTables ?? For a minor upgrade do we >> need to run upgrade stables?? >> >> I knew when we are doing a major upgrade we have to run upgrade sstables >> so that sstables will be re-written to newer version with additional meta >> data. >> >> But do we need to run upgrade sstables for upgrading from let's say >> 3.0.15 to 3.0.16 or 3.0.y to 3.11.y?? >> >> >> Thanks >> Pranay >> > > > > -- > > *Christophe Schmitz - **VP Consulting* > > AU: +61 4 03751980 / FR: +33 7 82022899 <+33%207%2082%2002%2028%2099> > > <https://www.facebook.com/instaclustr> > <https://twitter.com/instaclustr> > <https://www.linkedin.com/company/instaclustr> > > Read our latest technical blog posts here > <https://www.instaclustr.com/blog/>. This email has been sent on behalf > of Instaclustr Pty. Limited (Australia) and Instaclustr Inc (USA). This > email and any attachments may contain confidential and legally > privileged information. If you are not the intended recipient, do not copy > or disclose its content, but please reply to this email immediately and > highlight the error to the sender and then immediately delete the message. >