On 3/24/2018 11:22 AM, Hendrik Haddorp wrote:
below is the full entry from the Solr log. I actually also found the list of implicit request handlers later on. But that does make it even more strange that Solr complains about a missing handler.
The "not found" is rather generic, and might not be referring to the handler. I wonder if we can improve those not found messages to indicate *what* wasn't found.
2018-03-22 18:19:25.599 ERROR (updateExecutor-3-thread-7-processing-n:search-agent3:9007_solr x:collection-0005_shard1_replica_n2 s:shard1 c:collection-0005 r:core_node4) [c:collection-0005 s:shard1 r:core_node4 x:collection-0005_shard1_replica_n2] o.a.s.c.SyncStrategy http://search-agent3:9007/solr/collection-0005_shard1_replica_n2/: Could not tell a replica to recover:org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://search-agent3:9007/solr: Unable to locate core collection-0005_shard1_replica_n1
Based on the end of what I quoted here, I think that the issue here might be that the *core* doesn't exist, not that the handler doesn't exist. Which may mean that the info in zookeeper doesn't match the cores that are actually present and working.
If the core does exist on the disk, maybe Solr had a problem getting the core started.
Thanks, Shawn
