On Apr 23, 2013, at 2:49 PM, Shawn Heisey <s...@elyograg.org> wrote:
> What exactly is the 'request proxying' thing that doesn't work on tomcat? Is > this something different from basic SolrCloud operation where you send any > kind of request to any server and they get directed where they need to go? I > haven't heard of that not working on tomcat before. Before 4.2, if you made a read request to a node that didn't contain part of the collection you where searching, it would return 404. Write requests would be forwarded to where they belong no matter what node you sent them to, but read requests required that node have a part of the collection you were accessing. In 4.2 we added request proxying for this read side case. If a piece of the collection you are querying is not found on the node you hit, a simple proxy of the request is done to a node that does contain a piece of the collection. - Mark
