We ended up using a simple method to copy the directory directly to the node that was not deleted, then delete the solr data from zookeeper and restart it to achieve the effect. Thank you for your suggestion.
[image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&;> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&;> 18/06/25 上午9:40:22 2018-05-20 20:35 GMT+08:00 Erick Erickson <erickerick...@gmail.com>: > Simplest would be to host multiple shards on the same machine. Use > ADDREPLICA/DELETEREPLICA (collections API calls) to move the replicas > hosted on the nodes you want to use for another purpose and, when all > replicas are moved you can repurpose those machines. > > Another option would be to create a _new_ collection on the machines > you'll have dedicated to Solr with fewer shards, re-index all the > documents to the new machine and use collection aliasing (collections > API CREATEALIAS) to point to the new collection, then delete the old > collection. > > There are significantly more complex options to truly merge the > shards, but I wouldn't consider them until the above was proven to be > unsatisfactory. > > In any case, you need to be sure that the machines that remain are > powerful enough to host all the documents you've put on them. > > Best, > Erick > > On Sat, May 19, 2018 at 11:58 PM, 苗海泉 <mseaspr...@gmail.com> wrote: > > Hello everyone, I encountered a shard reduction problem with solr. My > > current solr cluster is deployed in solrcloud mode. Now I need to use > > several solr machines for other purposes. The solr version I use is Solr > > 6.0. What should I do? Do it, thank you for your help.-- > > ============================== > > 联创科技 > > 知行如一 > > ============================== > -- ============================== 联创科技 知行如一 ==============================
