Hi
You take all the risk by using unsupported features.
A supported way of achieving the same could perhaps be:
1) Create a new empty collection "gatewaycoll" on the nodes you want to
dedicate as "gateways"
2) Send your queries to the gateway collection but ask for data from the data
collection "datacoll"
http://some.solr.server:8983/solr/gatewaycoll?q=my query&collection=datacoll
Have not tested it but it should give the desired effect. You can hardcode the
"collection" param in solrconfig.xml of gatewaycoll's /select handler if you
wish
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 18. feb. 2019 kl. 08:59 skrev SOLR4189 <klin892...@yandex.ru>:
>
> I think, you don't understand what I mean.
>
> 1) I create collection with X shards, each shard has hash range (by CREATE
> collection command)
> 2) I add Y new shards in the same collection, each shard hasn't hash range,
> I call them gateways (by CREATE core command)
> 3) I add LoadBalancer over Y gateways, so all client queries will pass
> through gateways
>
> In this case, my Y gateways forward queries and merge results only (WITHOUT
> searching in their index) and my X shards search in index only (WITHOUT
> forward queries and merge results). It gives me the best queries
> performance.
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
