bq: What if I don't need NRT and in particular want the slave to use all resources for query answering, i.e. only the master shall index. But at the same time I want all the other benefits of SolrCloud.
You want all the benefits of SolrCloud without... using SolrCloud? Your only two choices are traditional master/slave or SolrCloud. SolrCloud indexes to all nodes all the time, there's no real way to turn that off. You _can_ control the frequency of commits but you can't turn off the indexing to all the nodes. FWIW, Erick On Tue, Jul 29, 2014 at 5:41 AM, Mikhail Khludnev < mkhlud...@griddynamics.com> wrote: > I never did it, but always like. > > http://lucene.472066.n3.nabble.com/Best-practice-for-rebuild-index-in-SolrCloud-td4054574.html > From time to time such recipes are mentioned in the list. > > > On Tue, Jul 29, 2014 at 12:39 PM, Harald Kirsch <harald.kir...@raytion.com > > > wrote: > > > Hi all, > > > > from the Solr documentation I find two options how replication of an > > indexing is handled: > > > > a) SolrCloud indexes on master and all slaves in parallel to support NRT > > (near realtime search) > > > > b) Legacy replication where only the master does the indexing and slave > > receive index copies once in a while. > > > > What if I don't need NRT and in particular want the slave to use all > > resources for query answering, i.e. only the master shall index. But at > the > > same time I want all the other benefits of SolrCloud. > > > > Is this setup possible? Is it somewhere described in the docs? > > > > Thanks, > > Harald. > > > > > > -- > Sincerely yours > Mikhail Khludnev > Principal Engineer, > Grid Dynamics > > <http://www.griddynamics.com> > <mkhlud...@griddynamics.com> >
