[
https://issues.apache.org/jira/browse/SOLR-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207039#comment-13207039
]
Mark Miller commented on SOLR-3131:
-----------------------------------
This is because when not a slave we don't have a permanent SnapPuller, but
instead create a tmp one on the fetch index cmd - but other status calls, like
details, only look for the permanent SnapPuller (which is null in the above
case).
It's all somewhat by design it would seem, but of course could be improved
(even if we don't support it, it shouldn't NPE, and supporting it would be
nice).
> "details" command fails while a replication is forced with a "fetchIndex"
> command on a non-slave server
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3131
> URL: https://issues.apache.org/jira/browse/SOLR-3131
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 4.0
> Reporter: Tomás Fernández Löbbe
> Priority: Minor
>
> Steps to reproduce the problem:
> 1) Start a master Solr instance (called A)
> 2) Start a Solr instance with replication handler configured, but with no
> "slave" configuration. (called B)
> 3) Issue the request
> http://B:port/solr/replication?command=fetchindex&masterUrl=http://A:port/solr/replication
> 4) While B is fetching the index, issue the request:
> http://B:port/solr/replication?command=details
> Expected behavior: See the replication details as usual.
> Getting an exception instead:
> java.lang.NullPointerException
> at
> org.apache.solr.handler.ReplicationHandler.isPollingDisabled(ReplicationHandler.java:447)
> at
> org.apache.solr.handler.ReplicationHandler.getReplicationDetails(ReplicationHandler.java:611)
> at
> org.apache.solr.handler.ReplicationHandler.handleRequestBody(ReplicationHandler.java:211)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:1523)
> at
> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:339)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:234)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
