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 that's already been worked out, namely ADDREPLICA. If you need to precisely place all replicas, you can create the collection with the EMPTY node set and then add one replica at a time, placing it precisely where you want. You can also control replica placement on the CREATE command. Best, Erick On Tue, Feb 12, 2019 at 9:06 AM SOLR4189 <klin892...@yandex.ru> wrote: > > 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://<server_name>:<port>/solr/admin/cores?action=create&name=<collection_name>&shard=<shard_name>* > > So always I got Y cores with the same name (collection name) and due to > CREATESNAPSHOT command doesn't work. > > Solution is to use something like this if you need to add new cores after > creating collection: > *http://<server_name>:<port>/solr/admin/cores?action=create&name=<collection_name>_<shard_name>&collection=<collection_name>&shard=<shard_name>* > > > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
