Thanks Erick,
While it probably does not have any major impact on performance, I think solely
to avoid a single point of failure on the main shard it makes sense to load
balance it.
Regards,
Ryan Tabora
On Jun 4, 2012, at 2:51 AM, Erick Erickson [via Lucene] wrote:
> The "main" shard has some
The "main" shard has some extra work to do. Namely
1> create the sub-requests
2> collate the results from all the sub-requests (including itself).
But this work is generally a small amount of the actual work being
done, so it's often unnoticeable.
That said, I'd just put all my slaves behind a lo
Hey Erick,
It looks like the thread you mentioned talks about how to configure the
shards parameter in the Solr query. I am more interested in the 'main' shard
you query against when you make Solr queries (main shard being the shard you
direct the query against,
mainshard/select?q=*:*&shards=shard
People usually just have the slaves know about each other via the
configuration files (here's a good reference as well as a gotcha,
http://lucene.472066.n3.nabble.com/how-to-have-quot-shards-quot-parameter-by-default-td884519.html).
The idea is that you configure a search handler to automatically
