lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <>
Subject [jira] [Commented] (SOLR-7642) Should launching Solr in cloud mode using a ZooKeeper chroot create the chroot znode if it doesn't exist?
Date Sat, 06 Jun 2015 18:20:00 GMT


Tomás Fernández Löbbe commented on SOLR-7642:

Yes, this was discussed in SOLR-4028 and the decision there was to only create the chroot
when bootstrap_conf was used, don't know how the correct way should be now that we have the

I think this would give us something easier to start at the cost of increasing the possibility
of a development/production headache (e.g. due to a typo, or you are hitting the wrong ZooKeeper
ensemble, etc). On the other hand, it would be nice to not need to use the or equivalent
to create the chroot

> Should launching Solr in cloud mode using a ZooKeeper chroot create the chroot znode
if it doesn't exist?
> ---------------------------------------------------------------------------------------------------------
>                 Key: SOLR-7642
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Timothy Potter
>            Priority: Minor
> If you launch Solr for the first time in cloud mode using a ZooKeeper connection string
that includes a chroot leads to the following initialization error:
> {code}
> ERROR - 2015-06-05 17:15:50.410; [   ] org.apache.solr.common.SolrException;
A chroot was specified in ZkHost but the znode doesn't exist. localhost:2181/lan
>         at org.apache.solr.core.ZkContainer.initZooKeeper(
>         at org.apache.solr.core.CoreContainer.load(
>         at org.apache.solr.servlet.SolrDispatchFilter.createCoreContainer(
>         at org.apache.solr.servlet.SolrDispatchFilter.init(
>         at org.eclipse.jetty.servlet.FilterHolder.initialize(
>         at org.eclipse.jetty.servlet.ServletHandler.initialize(
>         at org.eclipse.jetty.servlet.ServletContextHandler.startContext(
>         at org.eclipse.jetty.webapp.WebAppContext.startWebapp(
>         at org.eclipse.jetty.webapp.WebAppContext.startContext(
>         at org.eclipse.jetty.server.handler.ContextHandler.doStart(
>         at org.eclipse.jetty.webapp.WebAppContext.doStart(
> {code}
> The work-around for this is to use the scripts/cloud-scripts/ script to create
the chroot znode (bootstrap action does this).
> I'm wondering if we shouldn't just create the znode if it doesn't exist? Or is that some
violation of using a chroot?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message