The ConcurrentUpdateSolrClient is not cloud aware or takes zkHostString as input. So only option is to use CloudSolrClient with SolrJ & Thread pool executor framework.
On Thu, Oct 8, 2015 at 12:50 PM, Alessandro Benedetti < benedetti.ale...@gmail.com> wrote: > This depends of the number of active producers, but ideally it's ok. > Different threads will access the ThreadSafe ConcurrentUpdateSolrClient and > send the document in batches. > > Or you were meaning something different ? > > > On 8 October 2015 at 16:00, Mugeesh Husain <muge...@gmail.com> wrote: > > > Good way Using SolrJ with Thread pool executor framework, increase number > > of > > Thread as per your requirement > > > > > > > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/Best-Indexing-Approaches-To-max-the-throughput-tp4232740p4233513.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > > > > > -- > -------------------------- > > Benedetti Alessandro > Visiting card - http://about.me/alessandro_benedetti > Blog - http://alexbenedetti.blogspot.co.uk > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England >
