If a replica is in the DOWN status, it means it cannot move to the RECOVERING status. It's either failed somehow, hit a bug, is replaying transaction logs, or something else. You have to look at the logs to determine why a replica won't come out of the DOWN state usually. ... View more

Can you paste the command you tried when being explicit?   I would say the likely problem is that you should use the following zk address:   SOLR_ZK_ENSEMBLE=master:2181,n1:2181/solr CM will use a root of /solr by default - you need to chroot onto that node, and so your final address in the ensemble string should include the chroot. To inspect ZooKeeper you have many options. If Solr is up, you can inspect ZooKeeper via it's admin UI. Solr has to be able to connect to ZooKeeper first though - and will see a limited chroot'd view. ZooKeeper also comes with some simple command line tools - you can get started with those here: http://zookeeper.apache.org/doc/r3.4.5/zookeeperStarted.html There are also some graphical tools - I like to use a plugin for eclipse to browse ZK. Google should provide some other alternatives. ... View more

Make sure your /etc/default/solr SOLR_ZK_ENSEMBLE property is set the same as CM. CM uses a /solr zk chroot by default, so make sure that chroot is also used in the /etc/default/solr config. Alternatively, you can pass an explicit zk address when making the call via:   solrctl --zk zkaddress:port/solr instancedir --create collection1 $HOME/solr_configs   To debug this, you might want to use a tool to inspect ZooKeeper. The configuration files that you uploaded should be in /solr/configs/{name}. Do you see anything there - or perhaps you see it in /configs/{name}? That would likely be the case if the configured chroots did not match.   - Mark ... View more