There is an additional limitation to the current HTTP limitation, in that it does a boolean OR of all the uniq keys it needs to fetch on remote shards Once you query for ~100 or so documents, the URL can grow to > 10000 characters long, and Java refuses to open it. To make it work we'd need to be able to POST to Solr for results, which I don't think is possible yet...
I completely agree that using some kind of remote procedure call for queries to other shards makes sense. Perhaps we should attempt to "merge" the RMI backend of SOLR-255 with the high level approach taken in SOLR-303? Or do you have more experience with other brands of RPC? Thanks a lot, Stu -----Original Message----- From: Yonik Seeley <[EMAIL PROTECTED]> Sent: Friday, September 21, 2007 2:53pm To: [EMAIL PROTECTED] Subject: Re: HTTP or RMI, Jini, JavaSpaces for distributed search On 9/21/07, Walter Underwood wrote: > Please don't switch to RMI. We've spent the past year converting > our entire middle tier from RMI to HTTP. We are so glad that we > no longer have any RMI servers. Just to be clear for everyone, this wouldn't be a front-end change... HTTP load balancer over top-level searches would still be the normal way to do HA / query-load scaling. This is more about traffic between Solr servers themselves for distributed search (something that doesn't even exist yet). -Yonik
