Get Outlook for Android<https://aka.ms/ghei36>
________________________________ From: Gell-Holleron, Daniel <daniel.gell-holle...@gb.unisys.com> Sent: Monday, September 2, 2019 8:04:42 AM To: solr-user@lucene.apache.org <solr-user@lucene.apache.org> Subject: [EXTERNAL] RE: ZooKeeper error in solr.log Hello, The error I get in the log is below: 2019-09-02 09:17:22.812 ERROR (qtp1192171522-16) [ ] o.a.s.h.RequestHandlerBase java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.solr.handler.admin.ZookeeperStatusHandler.monitorZookeeper(ZookeeperStatusHandler.java:185) at org.apache.solr.handler.admin.ZookeeperStatusHandler.getZkStatus(ZookeeperStatusHandler.java:99) at org.apache.solr.handler.admin.ZookeeperStatusHandler.handleRequestBody(ZookeeperStatusHandler.java:77) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:199) at org.apache.solr.servlet.HttpSolrCall.handleAdmin(HttpSolrCall.java:796) at org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:762) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:522) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:397) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:343) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1602) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1588) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1557) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:502) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) at java.lang.Thread.run(Unknown Source) To confirm is this the setting 4lw.commands.whitelist=mntr,conf,ruok? I am running ZooKeeper version 3.5.5 Thanks, Daniel -----Original Message----- From: Shawn Heisey <apa...@elyograg.org> Sent: 02 September 2019 12:25 To: solr-user@lucene.apache.org Subject: Re: ZooKeeper error in solr.log On 9/2/2019 4:03 AM, Gell-Holleron, Daniel wrote: > I'm having trouble retrieving ZK status in SolrCloud. > > As far as I know, I've followed all configuration instructions. > > The ZK_HOST, ZK_CLIENT_TIMEOUT and SOLR_HOST settings are configured > along with a myid file in the data directory. The zoo.cfg contains the > following: > > tickTime=2000 > dataDir=C:\\apps\\zookeeper\\data > clientPort=2181 > initLimit=5 > syncLimit=2 > server.1=server1:2888:3888 > server.2=server2:2888:3888 > autopurge.snapRetainCount=3 > autopurge.purgeInterval=1 > > I'm using Solr 8.1 for Windows, which is running on Java 8. Log file > attached. The log file is NOT attached. The mailing list eats almost all attachments. The ZK version of your ZK servers is not here. If the ZK version is 3.5.x, you will need a new option in the server config. But you'll still have a problem, because you have a multi-server ensemble, and ZK 3.5 changes the output for that in a way that Solr can't handle. The second problem will be fixed in Solr 8.3 when it is released. https://issues.apache.org/jira/browse/SOLR-8346?focusedCommentId=16888877&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16888877 https://issues.apache.org/jira/browse/SOLR-13672 Side note: A 2-server ZK ensemble is actually LESS fault tolerant than a single server. For fault tolerance, you need three ZK servers. Thanks, Shawn Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.