Re: Collections API timeout

Yes, I've checked them and all nodes are pointing to the sme IP and the same port (2181). Also all of them are visible in the SolrCloud Graph section so this would mean they are part of the same cloud. Largest file is solrconfig which is 58K so this shouldn't be a problem either. The potential

Re: Collections API timeout

Hmmm, I didn’t really look carefully at the end of your e-mail. There not being an /overseer znode _looks_ like one or more of your Solr nodes isn’t connecting to the proper ZooKeeper ensemble. bq. All of the instances are able to talk to zookeeper (they are > >>> displayed as active in the

Re: Collections API timeout

Hi Erick, thanks for your reply! I didn't mention it but we have tried async requests. Then it does not time out of course, but instead appears to run indefinitely, with REQUESTSTATUS response like this: { "responseHeader":{ "status":0, "QTime":1}, "status":{ "state":"submitted",

Re: Collections API timeout

Certainly at times some things just take a long time. The 180 second timeout is fairly arbitrary. GC pauses, creating a zillion replicas etc. can cause timeouts like this to be exceeded. Rather than rely on lengthening some magic timeout value and hoping, I suggest you use the async option,

Collections API timeout

Hi everyone, recently when trying to delete a collection we have noticed that all calls to the Collections API time out after 180s. Something similar is described here however restarting the instance or the server does