Scenario: You've got a simple proxy / load-balancer in front of your SolrCloud cluster that could hit any node in the cluster, or maybe it's just communicating with some. For diagnostic purposes, you want to reach a specific node to interrogate some of the node specific paths (perhaps metrics, say). But the place you do this request, perhaps your own workstation, cannot directly reach the Solr nodes. And the simple proxy has no mechanism to take such instruction.
Proposal: A simple Solr servlet filter that proxies when it sees a special header or URL param naming a live node in the cluster -- not to any node anywhere. Opt-in; not registered in web.xml by default. Is this useful to others? I already have something coded. It's quite simple because (A) it taps into Solr's existing request proxy functionality used for core/collection requests, and (B) no change to any part of Solr thanks to architectural improvements in Solr 10.1. It's up to a user (who must opt-in, remember) to weigh the security risks of their envornment. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
