Of course I did not mean to multiple cores of the same shard... A normal SolrCloud configuration, let's say 4 shards, on 4 servers, using replicationFactor=3. Of course, no matter what core was requested, the request will be forwarded to one core of each shard. My question is - whether this *first* request should be distributed over all of the cores in a specific server or not.
The statement "Cores are completely thread safe and can do queries/updates concurrently" answers me that there is no reason for my idea. On Mon, Feb 4, 2013 at 9:28 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 2/4/2013 12:06 PM, Isaac Hebsh wrote: > >> LBHttpSolrServer is only solrj feature.. doesn't it? >> >> I think that Solr does not balance queries among cores in the same server. >> You can claim that it's a non-issue, if a single core can completely serve >> multiple queries on the same time, and passing requests through different >> cores does nothing. I feel that we can achieve some improvement in this >> case... >> > > If LBHttpSolrServer is used as described in the Wiki (whoever wrote that > wasn't sure, they were asking), then it is being used on the server side, > not the client. > > Multiple copies of a shard on the same server is probably not a generally > supported config with SolrCloud. It would use more memory and disk space, > and I'm not sure that there would be any actual benefit to query speed. > Cores are completely thread safe and can do queries/updates concurrently. > Whatever concurrency problems exist are likely due to resource (CPU, RAM, > I/O) utilization rather than code limitations. If I'm right about that, > multiple copies would not solve the problem. Buying a bigger/faster server > would be the solution to that problem. > > Thanks, > Shawn > >
