lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isabelle Giguere (JIRA)" <j...@apache.org>
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 Mon, 22 Oct 2018 15:09:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659065#comment-16659065
] 

Isabelle Giguere commented on SOLR-7642:
----------------------------------------

Attached proposition (not tested ;) ), blending both [~smolloy] and [~janhoy] 's ideas.

It might be overkill ... what does anyone think ?
First, creating the chroot must be allowed (if createZkRoot=true), then, the ZK root must
match the authorized root (set by solr.zkChroot).
The name 'createZkRoot' could be changed to solr.createZkRoot, for uniformity.

> Should launching Solr in cloud mode using a ZooKeeper chroot create the chroot znode
if it doesn't exist?
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7642
>                 URL: https://issues.apache.org/jira/browse/SOLR-7642
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Timothy Potter
>            Priority: Minor
>         Attachments: SOLR-7642.patch, SOLR-7642.patch, SOLR-7642_tag_7.5.0.patch, SOLR-7642_tag_7.5.0_proposition.patch
>
>
> 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; null:org.apache.solr.common.cloud.ZooKeeperException:
A chroot was specified in ZkHost but the znode doesn't exist. localhost:2181/lan
>         at org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:113)
>         at org.apache.solr.core.CoreContainer.load(CoreContainer.java:339)
>         at org.apache.solr.servlet.SolrDispatchFilter.createCoreContainer(SolrDispatchFilter.java:140)
>         at org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:110)
>         at org.eclipse.jetty.servlet.FilterHolder.initialize(FilterHolder.java:138)
>         at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:852)
>         at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
>         at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
>         at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
>         at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
>         at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> {code}
> The work-around for this is to use the scripts/cloud-scripts/zkcli.sh 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message