Hi Dave, Three things to note: 1. The default timeout of 60s has been raised to 3 minutes in 4.7. Unfortunately, the timeout if not configurable. 2. The timeout happens because these commands execute on the overseer collection processor (actually the same node as overseer) in a single thread. So it doesn't matter whether data was being inserted or queries on a node. The timeout will happen if there is a long running command e.g. splitshard ahead of the deletealias or if there are a lot of items in the overseer queue. 3. SOLR-5477 and SOLR-5681 will help. SOLR-5477 has already been committed and the other is in the works. I hope we will get them out in 4.8
On Sat, Mar 29, 2014 at 2:16 AM, Dave Seltzer <dselt...@tveyes.com> wrote: > I just wanted to bump my question in hopes that someone would see it. > > Does anyone know how I might track down the cause of this timeout, or > perhaps extend the timeout? > > -D > > > On Thu, Mar 27, 2014 at 11:21 AM, Dave Seltzer <dselt...@tveyes.com> wrote: > >> I'm trying to delete some data on a 12 node Solr cloud environment. The >> cluster is running Solr 4.6.1. >> >> When I try to delete an alias the collections api returns: >> >> org.apache.solr.common.SolrException: deletealias the collection time >> out:60s at >> org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:204) >> at >> org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:185) >> at >> org.apache.solr.handler.admin.CollectionsHandler.handleDeleteAliasAction(CollectionsHandler.java:274) >> at >> org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:154) >> at >> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135) >> at >> org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:673) >> at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:261) >> at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:201) >> 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:533) >> 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:744) >> >> It doesn't seem to matter which server in the cluster I runt this on. >> There's no data being inserted and no queries being performed. >> >> I have the same problem whether I attempt to remove a collection or a >> collection alias. How do I find the source of this problem? >> >> Many Thanks, >> >> -D >> -- Regards, Shalin Shekhar Mangar.
