I believe the SolrJ code round robins which server the request is sent to and as such probably wouldn't send to the same server in your case, but if you had an HttpSolrServer for instance and were pointing to only one particular intsance my guess would be that would be 5 separate requests from the server you hit. Especially since in all likelihood those documents wouldn't be destined for the same shard as the others (unless of course you only had 1 shard and you sent these to the replica)
On Fri, Apr 20, 2012 at 3:02 PM, Darren Govoni <dar...@ontrenet.com> wrote: > Gotcha. > > Now does that mean if I have 5 threads all writing to a local shard, > will that shard piggyhop those index requests onto a SINGLE connection > to the leader? Or will they spawn 5 connections from the shard to the > leader? I really hope the former....the latter won't scale well. > > On Fri, 2012-04-20 at 10:28 -0400, Jamie Johnson wrote: >> my understanding is that you can send your updates/deletes to any >> shard and they will be forwarded to the leader automatically. That >> being said your leader will always be the place where the index >> happens and then distributed to the other replicas. >> >> On Fri, Apr 20, 2012 at 7:54 AM, Darren Govoni <dar...@ontrenet.com> wrote: >> > Hi, >> > I just wanted to make sure I understand how distributed indexing works >> > in solrcloud. >> > >> > Can I index locally at each shard to avoid throttling a central port? Or >> > all the indexing has to go through a single shard leader? >> > >> > thanks >> > >> > >> > >
