Something like this would be excellent. Right now I am starting up
the main server and then doing a wget to see if the server has started
successfully before firing off any secondary servers. If we could do
what you're saying then everything is much cleaner to do.
On Mon, Oct 3, 2011 at 1:20 AM,
I could use an easier way to do this myself:
https://issues.apache.org/jira/browse/SOLR-2805
I'm going to add a main method to ZkController that will make this simpler -
I've got an early version that works something like: java -classpath .:*
org.apache.solr.cloud.ZkController 127.0.0.1:9983 127.0
On Sep 29, 2011, at 1:59 PM, Jamie Johnson wrote:
> 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
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 obvi
