I think you should do your own measurements. This is very document and processing specific. You can run a test with a simple setup for let’s say 1 mio document and interpolate from this. It could be also that your ETL is the bottleneck and not Solr. At the same time you can simulate user queries using Jmeter or similar.
> Am 18.01.2020 um 09:05 schrieb Rajdeep Sahoo <rajdeepsahoo2...@gmail.com>: > > Our Index size is huge and in master slave the full indexing time is almost > 24 hrs. > In future the no of documents will increase. > So,please some one recommend about the no of nodes and configuration like > ram and cpu core for solr cloud. > >> On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood, <wun...@wunderwood.org> >> wrote: >> >> Why do you want to change to Solr Cloud? Master/slave is a great, stable >> cluster architecture. >> >> wunder >> Walter Underwood >> wun...@wunderwood.org >> http://observer.wunderwood.org/ (my blog) >> >>> On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo <rajdeepsahoo2...@gmail.com> >> wrote: >>> >>> Please reply anyone >>> >>> On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, < >> rajdeepsahoo2...@gmail.com> >>> wrote: >>> >>>> Hi all, >>>> We are using solr cloud 7.7.1 >>>> In a live production environment how many solr cloud server do we need, >>>> Currently ,we are using master slave set up with 16 slave server with >>>> solr 4.6. >>>> In solr cloud do we need to scale it up or 16 server will suffice the >>>> purpose. >>>> >>>> >> >>
