Hi @Bryan When you said "sizable amount of data" you meant a huge amount of data right? Our big table is in LCS and if we use the migration process we will need to run a repair seq over this table for a long time.
We are planning to go to repairs inc using the version 2.1.14 Saludos Jean Carlo "The best way to predict the future is to invent it" Alan Kay On Tue, Jun 21, 2016 at 4:34 PM, Vlad <qa23d-...@yahoo.com> wrote: > Thanks for answer! > > >It may still be a good idea to manually migrate if you have a sizable > amount of data > No, it would be brand new ;-) 3.0 cluster > > > > On Tuesday, June 21, 2016 1:21 AM, Bryan Cheng <br...@blockcypher.com> > wrote: > > > Sorry, meant to say "therefore manual migration procedure should be > UNnecessary" > > On Mon, Jun 20, 2016 at 3:21 PM, Bryan Cheng <br...@blockcypher.com> > wrote: > > I don't use 3.x so hopefully someone with operational experience can chime > in, however my understanding is: 1) Incremental repairs should be the > default in the 3.x release branch and 2) sstable repairedAt is now properly > set in all sstables as of 2.2.x for standard repairs and therefore manual > migration procedure should be necessary. It may still be a good idea to > manually migrate if you have a sizable amount of data and are using LCS as > anticompaction is rather painful. > > On Sun, Jun 19, 2016 at 6:37 AM, Vlad <qa23d-...@yahoo.com> wrote: > > Hi, > > assuming I have new, empty Cassandra cluster, how should I start using > incremental repairs? Is incremental repair is default now (as I don't see > *-inc* option in nodetool) and nothing is needed to use it, or should we > perform migration procedure > <http://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsRepairNodesMigration.html> > anyway? And what happens to new column families? > > Regards. > > > > > >
