I am trying to automate the startup/shutdown of SolrCloud shards and
have noticed that there is a bit of a timing issue where if the server
which is to bootstrap ZK with the configs does not complete it's
process (i.e. there is no data at the Conf yet) the other servers will
fail to start.  An obvious solution is to just start the solr instance
responsible for bootstraping first, is there some way that folks are
handling this now?

Reply via email to