or https://issues.apache.org/jira/browse/CASSANDRA-8611 perhaps
All the best, [image: datastax_logo.png] <http://www.datastax.com/> Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] <https://www.linkedin.com/company/datastax> [image: facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] <https://twitter.com/datastax> [image: g+.png] <https://plus.google.com/+Datastax/about> <http://feeds.feedburner.com/datastax> <http://cassandrasummit-datastax.com/?utm_campaign=summit15&utm_medium=summiticon&utm_source=emailsignature> DataStax is the fastest, most scalable distributed database technology, delivering Apache Cassandra to the world’s most innovative enterprises. Datastax is built to be agile, always-on, and predictably scalable to any size. With more than 500 customers in 45 countries, DataStax is the database technology and transactional backbone of choice for the worlds most innovative companies such as Netflix, Adobe, Intuit, and eBay. On Mon, Aug 31, 2015 at 5:24 PM, Eric Evans <eev...@wikimedia.org> wrote: > > On Mon, Aug 31, 2015 at 1:32 PM, Sachin Nikam <skni...@gmail.com> wrote: > >> When we add 3 more nodes in Data Center B, the repair tool starts syncing >> the data between 2 data centers and then gives up after ~2 days. >> >> Has anybody run in to similar issue before? If so what is the solution? >> > > https://issues.apache.org/jira/browse/CASSANDRA-9624, maybe? > > > -- > Eric Evans > eev...@wikimedia.org >
