Re: CLUSTERSTATUS timeout
I'm also getting this error with 5.1.0 and a 27 shard setup. null:org.apache.solr.common.SolrException: CLUSTERSTATUS the collection time out:180s at org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:740) at org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:692) at org.apache.solr.handler.admin.CollectionsHandler.handleClusterStatus(CollectionsHandler.java:1042) at org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:259) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143) at org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:783) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:282) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:220) 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) Just another data point. -Joe On 12/17/2014 8:44 AM, adfel70 wrote: Hi Jonathan, We are having the exact same problem with Solr 4.8.0. Did you manage to resolve this one? Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/CLUSTERSTATUS-timeout-tp4173224p4174741.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: CLUSTERSTATUS timeout
Hi Jonathan, We are having the exact same problem with Solr 4.8.0. Did you manage to resolve this one? Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/CLUSTERSTATUS-timeout-tp4173224p4174741.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: CLUSTERSTATUS timeout
Hi Jonathan, That shouldn't happen. The API returns the answer from the Overseer node (via ZK) and should return immediately. The API will timeout after 180s if somehow it cannot get a response from Overseer. I don't see why it would timeout. What's the read timeout on your monitoring system? About your shards getting marked as down, do you send commits explicitly? If yes, you may be running into SOLR-6530 which is fixed in 4.10.2. On Mon, Dec 8, 2014 at 9:45 PM, Hutchins, Jonathan jhutch...@webmd.net wrote: We are currently running Solr 4.10.0 in production. We have run into an issue where we cannot have our monitoring system hit the CLUSTERSTATUS api command every five minutes (or even as long as every hour) without getting a significant number of timeouts on the command. Does this command return a timeout message after a period of time (and we aren’t waiting long enough) or will it hang indefinitely? This is a major problem for us because we are finding that shards will randomly get marked down, turn red in the web console, but there is no indication that they are down except if we run that command. Please help! Thanks! - Jonathan -- Regards, Shalin Shekhar Mangar.
CLUSTERSTATUS timeout
We are currently running Solr 4.10.0 in production. We have run into an issue where we cannot have our monitoring system hit the CLUSTERSTATUS api command every five minutes (or even as long as every hour) without getting a significant number of timeouts on the command. Does this command return a timeout message after a period of time (and we aren’t waiting long enough) or will it hang indefinitely? This is a major problem for us because we are finding that shards will randomly get marked down, turn red in the web console, but there is no indication that they are down except if we run that command. Please help! Thanks! - Jonathan
