Re: Incremental Repair Migration

2017-01-10 Thread Bhuvan Rawal
gh > > > > *From:* Jonathan Haddad [mailto:j...@jonhaddad.com] > *Sent:* Tuesday, January 10, 2017 11:50 AM > *To:* user@cassandra.apache.org > *Subject:* Re: Incremental Repair Migration > > > > Your best bet is to just run repair constantly. We maintain an updated &g

Re: Incremental Repair Migration

2017-01-10 Thread Jonathan Haddad
o any quick method to reduce that ? > > > > Regards > > Amit Singh > > > > *From:* Jonathan Haddad [mailto:j...@jonhaddad.com] > *Sent:* Tuesday, January 10, 2017 11:50 AM > *To:* user@cassandra.apache.org > *Subject:* Re: Incremental Repair Migration > > >

RE: Incremental Repair Migration

2017-01-09 Thread Amit Singh F
will take hours to be finished if we go ahead with procedure shared by Datastax. So any quick method to reduce that ? Regards Amit Singh From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Tuesday, January 10, 2017 11:50 AM To: user@cassandra.apache.org Subject: Re: Incremental Repair Migration

Re: Incremental Repair Migration

2017-01-09 Thread Jonathan Haddad
Your best bet is to just run repair constantly. We maintain an updated fork of Spotify's reaper tool to help manage it: https://github.com/thelastpickle/cassandra-reaper On Mon, Jan 9, 2017 at 10:04 PM Amit Singh F wrote: > Hi All, > > > > We are thinking of migrating