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 <i...@mrcalonso.com> wrote: > Replies inline > > Carlos Alonso | Software Engineer | @calonso <https://twitter.com/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 >> > > -- Regards, Ryan Svihla
