Hi Ahmed Eljami, Problem is not only number of nodes. what is your capacity per node ? recommandations from Datastax is keeping data per node near or below 1 TB. Exceeding this value has the following effects:
- .Extremely long times (days) for bootstrapping new nodes. - .Impacts maintenance (day-to-day operations), such as recovering, adding, and replacing nodes. - .Reduces efficiency when running repairs. - .Significantly extends the time it takes to expand datacenters. - .Substantially increases compactions per node. Higher capacity nodes works best with static data and low access rates. Best regards _____________________________________________________________ [image: https://www.facebook.com/DMN-BigData-371074727032197/?modal=admin_todo_tour] <https://www.facebook.com/DMN-BigData-371074727032197/?modal=admin_todo_tour> <https://twitter.com/dmnbigdata> <https://www.instagram.com/> <https://www.linkedin.com/in/dngaya/> *Dieudonne Madishon NGAYA* Datastax, Cassandra Architect *P: *7048580065 *w: *www.dmnbigdata.com *E: *dmng...@dmnbigdata.com *Private E: *dmng...@gmail.com *A: *Charlotte,NC,28273, USA On Wed, Mar 13, 2019 at 11:58 AM Ahmed Eljami <ahmed.elj...@gmail.com> wrote: > Hi, > > We are planning to add a third datacenter to our cluster (already has 2 > datacenter, every datcenter has 50 nodes, so 100 nodes in total). > > My fear is that an important number of nodes per cluster (> 100) could > cause a lot of problems like gossip duration, maintenance (repair...)... > > I know that it depends on use cases, volume of data and many other thing, > but I would like that you share your experiences with that. > > Thx > > > >
