On 6/20/2017 9:46 AM, Aman Deep Singh wrote: > Sorry Shawn, > It didn't copy entire stacktrace I put the stacktrace at > https://www.dropbox.com/s/zf8b87m24ei2ils/solr%20exception2?dl=0 > > Note: I have shaded the solr library under com.gdn.solr620 so all solr > class will be appear as com.gdn.solr620.org.apache.solr.*
Wow, I really dropped the ball here. The thread is nearly a year old. I somehow missed the reply. I am sorry about that! Thank Alessandro for reviving the thread and making it clear that I never replied. This is the innermost cause: Caused by: org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = Session expired for /collections/productCollection/state.json Either there are network issues talking to ZooKeeper, or something else caused a timeout. Solr's default ZK client timeout when it is not configured is 15 seconds. In recent versions, the example configurations have an explicit setting of 30 seconds. Solr's zkClientTimeout is used to set ZooKeeper's sessionTimeout, and that's what is exceeded when a session expires. When this kind of error happens, it means something has gone VERY wrong -- 15 seconds is a REALLY long time when programs are trying to talk to each other. One common cause of problems like this is extreme GC pauses. Typically a pause problem capable of causing a ZK timeout would be due to the heap being too small, but it's always possible that it could happen because the heap is VERY large. Errors on the client side may not be as informative as corresponding errors in the solr.log file on the server(s). It would be a good idea to check solr.log for errors as well. Thanks, Shawn
