On 1/2/2018 12:55 PM, Alessandro Hoss wrote: > Actually I haven't tried the bin/solr script because I do everything > remotely on Solr. Thanks for the tip, it worked the way I want > (copying the conf to a new folder), but I need to do it through an API > and choosing what configset to copy from.
<snip> > That's exactly what I need. I've tried the Collections API, but it > doesn't > work when running on standalone mode (Doesn't it make sense to work > and emulates the behavior of SolrCloud in standalone mode?). The Collections API and the entire "collection" abstraction are features of SolrCloud. If you're not running in cloud mode, those are not available. If you want to do absolutely everything remotely without accessing the filesystem on the Solr server at all, then you're going to have to run SolrCloud. The thing that makes all this possible in cloud mode is ZooKeeper. All configurations and cluster state information are in the zookeeper database when Solr is running in cloud mode. Cores created via the API in cloud mode do not have a conf directory, and any conf directories that are manually created are ignored. https://zookeeper.apache.org/ For a fully fault-tolerant setup, ZooKeeper requires three separate physical machines. A minimum of two Solr machines are required for fault tolerance. The smallest possible fault-tolerant SolrCloud setup is three machines. Two of them would run both Solr and ZooKeeper, the third would run ZooKeeper only. Depending on the nature of the clients that access Solr, you might also need a load balancer. If you want a single-server setup that's not redundant, you can run Solr with an embedded ZooKeeper server. This is not recommended for production, but can be useful for dev or staging. Thanks, Shawn
