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
