You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Julien DAVID - Decalog <j....@decalog.net> on 2015/11/04 11:37:03 UTC
collection API timeout
Hi all,
We have a production environment composed by 6 solrcloud server and 3
zookeeper.
We've got around 30 collections, with 6 shards each.
We recently moved from 3 solr to 6, splitting the shards (3 to 6).
As the last weeks were a low period we didn't noticed any problem.
But since monday, the API collections calls go systematically to timeout.
We use calls to CLUSTERSTATUS, but LIST or OVERSEERSTATUS has the same
results, whatever the node.
We don't have any problem on the qualification environment which is
identical, except the load.
The error message is :
<lst name="error"><str name="msg">CLUSTERSTATUS the collection time
out:180s</str><str name="trace">org.apache.solr.common.SolrException:
CLUSTERSTATUS the collection time out:180s
at
org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:368)
at
org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:320)
at
org.apache.solr.handler.admin.CollectionsHandler.handleClusterStatus(CollectionsHandler.java:639)
at
org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:220)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
at
org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:729)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:267)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:368)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at
org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
at
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640)
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at
org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
at
org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:745)
Thanks for your help
--
Julien
Re: collection API timeout
Posted by Erick Erickson <er...@gmail.com>.
You may be hitting: https://issues.apache.org/jira/browse/SOLR-7459
(linked to https://issues.apache.org/jira/browse/SOLR-7049)...
Best,
Erick
On Wed, Nov 4, 2015 at 5:00 AM, Julien David <j....@decalog.net> wrote:
> I forgot to mention that we are using Solr 4.9.0 and zookeeper 3.4.6
>
> Thanks
>
> Julien
>
>
> Le 04/11/2015 11:37, Julien DAVID - Decalog a écrit :
>>
>> Hi all,
>>
>> We have a production environment composed by 6 solrcloud server and 3
>> zookeeper.
>> We've got around 30 collections, with 6 shards each.
>> We recently moved from 3 solr to 6, splitting the shards (3 to 6).
>>
>> As the last weeks were a low period we didn't noticed any problem.
>> But since monday, the API collections calls go systematically to timeout.
>> We use calls to CLUSTERSTATUS, but LIST or OVERSEERSTATUS has the same
>> results, whatever the node.
>>
>> We don't have any problem on the qualification environment which is
>> identical, except the load.
>>
>> The error message is :
>> <lst name="error"><str name="msg">CLUSTERSTATUS the collection time
>> out:180s</str><str name="trace">org.apache.solr.common.SolrException:
>> CLUSTERSTATUS the collection time out:180s
>> at
>> org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:368)
>> at
>> org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:320)
>> at
>> org.apache.solr.handler.admin.CollectionsHandler.handleClusterStatus(CollectionsHandler.java:639)
>> at
>> org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:220)
>> at
>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:729)
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:267)
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
>> at
>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
>> at
>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455)
>> at
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
>> at
>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
>> at
>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
>> at
>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
>> at
>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384)
>> at
>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
>> at
>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
>> at
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>> at
>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
>> at
>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
>> at
>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>> at org.eclipse.jetty.server.Server.handle(Server.java:368)
>> at
>> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
>> at
>> org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
>> at
>> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942)
>> at
>> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004)
>> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640)
>> at
>> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>> at
>> org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
>> at
>> org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)
>> at
>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>> at
>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>> Thanks for your help
>>
>> --
>> Julien
>>
>>
>>
>
>
>
Re: collection API timeout
Posted by Erick Erickson <er...@gmail.com>.
You should be able to go straight to 5.3.1
Solr/Lucene tries to guarantee that the indexes are readable
one major version back, i.e. 5.x Solr/Lucene code should
be able to read any 4.x index. New segments are written in the
most modern format, so over time all the 4x remnants should
disappear.
You can also use the IndexUpgrader tool to make upgrade
the index, see:
https://lucene.apache.org/core/5_3_1/core/org/apache/lucene/index/IndexUpgrader.html
take a backup first of course ;)
You can also optimize after upgrading to 5.3.1 which will rewrite
all the segments too, but personally I'd run the IndexUpgrade
by preference unless it's an index that doesn't change very often if
at all.
All that said, you should simply be able to install 5.3.1 and start
running, running
the IndexUpgrade tool or optimizing isn't actually necessary.
Best,
Erick
On Thu, Nov 5, 2015 at 1:28 AM, Julien David <j....@decalog.net> wrote:
> Seems I'ill need to upgrade to 5.3.1
>
> It is possible to upgrade from 4.9 to 5.3 or do I need deploy all
> intermediate versions?
>
> Thks
>
>
>
>>
>
>
>
Re: collection API timeout
Posted by lboutros <bo...@gmail.com>.
Hi Julien,
just one additional thing,
if you developed some plugins/filters, you will have to adapt and compile
them for the Solr 5 API.
Ludovic.
-----
Jouve
France.
--
View this message in context: http://lucene.472066.n3.nabble.com/collection-API-timeout-tp4238150p4238511.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: collection API timeout
Posted by Julien David <j....@decalog.net>.
Seems I'ill need to upgrade to 5.3.1
It is possible to upgrade from 4.9 to 5.3 or do I need deploy all
intermediate versions?
Thks
>
Re: collection API timeout
Posted by Julien David <j....@decalog.net>.
I forgot to mention that we are using Solr 4.9.0 and zookeeper 3.4.6
Thanks
Julien
Le 04/11/2015 11:37, Julien DAVID - Decalog a écrit :
> Hi all,
>
> We have a production environment composed by 6 solrcloud server and 3
> zookeeper.
> We've got around 30 collections, with 6 shards each.
> We recently moved from 3 solr to 6, splitting the shards (3 to 6).
>
> As the last weeks were a low period we didn't noticed any problem.
> But since monday, the API collections calls go systematically to timeout.
> We use calls to CLUSTERSTATUS, but LIST or OVERSEERSTATUS has the same
> results, whatever the node.
>
> We don't have any problem on the qualification environment which is
> identical, except the load.
>
> The error message is :
> <lst name="error"><str name="msg">CLUSTERSTATUS the collection time
> out:180s</str><str name="trace">org.apache.solr.common.SolrException:
> CLUSTERSTATUS the collection time out:180s
> at
> org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:368)
> at
> org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:320)
> at
> org.apache.solr.handler.admin.CollectionsHandler.handleClusterStatus(CollectionsHandler.java:639)
> at
> org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:220)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
> at
> org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:729)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:267)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:368)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
> at
> org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640)
> at
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
> at
> org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72)
> at
> org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:745)
>
>
> Thanks for your help
>
> --
> Julien
>
>
>