[jira] [Resolved] (SOLR-11851) Issue After adding another node in Apache Solr Cluster

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (SOLR-11851) Issue After adding another node in Apache Solr Cluster

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erick Erickson resolved SOLR-11851.
-----------------------------------
    Resolution: Not A Problem

Please raise this question on the user's list at [hidden email], see: (http://lucene.apache.org/solr/community.html#mailing-lists-irc) there are a _lot_ more people watching that list who may be able to help.

If it's determined that this really is a code issue in Solr and not a configuration/usage problem, we can raise a new JIRA or reopen this one.

When you do make the comment on the user's list, you need to include the error from the solr log in node3, that should give a better explanation about the cause of why that node didn't come up.


> Issue After adding another node in Apache Solr Cluster
> -------------------------------------------------------
>
>                 Key: SOLR-11851
>                 URL: https://issues.apache.org/jira/browse/SOLR-11851
>             Project: Solr
>          Issue Type: Test
>      Security Level: Public(Default Security Level. Issues are Public)
>          Components: Build
>    Affects Versions: 7.2
>         Environment: Red Hat Enterprise Linux Server release 7.4
> VM1 configured with-
> 1. Zookeeper1, 2 and 3 on different port
> 2. Solr 7.2 configured with 2 node and 2 shard and 2 replica
> VM2- New Server, we are trying to add in existing cluster. We followed the instruction from Apache Solr reference guide for 7.2. as below-
> unzip the Solr-7.2.0.tar.gz and-
> mkdir -p example/cloud/node3/solr
> cp server/solr/solr.xml example/cloud/node3/solr
> bin/solr start -cloud -s example/cloud/node3/solr -p 8987 -z <hostname VM1>:<zookeeper port>
>  
>            Reporter: Sushil Tripathi
>
> Environment Detail-
> ================
> Red Hat Enterprise Linux Server release 7.4
> VM1 configured with-
> 1. Zookeeper1, 2 and 3 on different port
> 2. Solr 7.2 configured with 2 node and 2 shard and 2 replica
> VM2- New Server, we are trying to add in existing cluster. We followed the instruction from Apache Solr reference guide for 7.2. as below-
> unzip the Solr-7.2.0.tar.gz and-
> mkdir -p example/cloud/node3/solr
> cp server/solr/solr.xml example/cloud/node3/solr
> bin/solr start -cloud -s example/cloud/node3/solr -p 8987 -z <hostname VM1>:<zookeeper port>
> Issue-
> =====
> while calling URL- http://10.0.12.57:8983/solr/
> It seems new node still not part of cluster also not having any core and indexes. Thanks for help in advance.
> Error -
> =====
> HTTP ERROR 404
> Problem accessing /solr/. Reason:
>     Not Found
> Caused by:
> javax.servlet.UnavailableException: Error processing the request. CoreContainer is either not initialized or shutting down.
> at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:342)
> at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326)
> at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
> at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> at org.eclipse.jetty.server.Server.handle(Server.java:534)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
> at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
> at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
> at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
> at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
> at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]