Currently distributed requests are entirely initiated by whichever node receives a query, correct? That is, as far as I know shards don't talk to each other or send requests back to the controller.
I'm looking at sending stats facets between shards to speed up merging. Rather than have one node responsible for merging the facet sets from every shard, each facet set is partitioned by term and then each shard merges one partition of each facet set. A-D, E-G, etc. However, that kind of communication doesn't really fit into Solr's current model of distributed processing. I think my use case isn't the only instance where it could help performance for shards to talk amongst themselves, so I'm curious why nothing in Solr does. Is it deliberate? No one bothered? I'm wrong and nothing else has a non-trivial reduce step? Steve McKay | Software Developer | GCE [email protected]<mailto:[email protected]> | (703) 390-3044 desk | (703) 659-0608 Skype | (443) 710-2762 mobile Connect with GCE: www.GCEcloud.com<http://www.gcecloud.com/> | Facebook<https://www.facebook.com/GCEcloud> | Twitter<https://twitter.com/GCECloud> | Google+<https://plus.google.com/u/0/112948441992350338884/posts> The information contained in this e-mail and any attachment(s) is Confidential, Privileged, Protected from any disclosure, and proprietary to Global Computer Enterprises, Inc. The person addressed in the email is the sole authorized recipient. If you are not the intended recipient, you are hereby notified that any review, use, disclosure, retransmission, dissemination, distribution, copying, or any other actions related to this information is strictly prohibited. If you have received this communication in error, please inform the sender and delete or destroy any copy of this message.
