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
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
You're going to continually run into issues if you use the _cores_ api
to add replicas to a _collection_.
True, the collection API ADDREPLICA command uses the _cores_ API to
add replicas, but someone else has already worked out all the finicky
details.
So do yourself a favor and use the mechanism
Ok. I understood my problem. Usually I create collection with X shards and
then add some Y cores. This Y cores I use like gateways or federators (my
web application sends queries to load balancer that connected to Y cores
only).
When I create Y cores, I used this command
*http://:/solr/admin/cores
Ok. I understood my problem. Usually I create collection with X shards and
then add some Y cores. This Y cores I use like gateways or federators (my
web application sends queries to load balancer that connected to Y cores
only).
When I create Y cores, I used this command
*http://:/solr/admin/cores
