On 2/5/2018 11:52 PM, A.Guptar wrote:
I have removed the -cloud from the startup script and restarted the server.
Issue still persists.
Attached is the solr.log file.
Normally attachments don't make it to the list, but it seems that Nabble
saved the day in this particular case. I was able to download the log
from a link that Nabble included.
Here's the message associated with the first ERROR entry in your log:
No config data found at path:
/collections/prod-project-engb-lowexposure-contents-staging
That path location is within the ZooKeeper database. That location in
the database should contain a small amount of JSON text, defining a
"configName" key with a value that is a configuration name. This error
message is saying that either that location in the ZK database doesn't
exist, or it doesn't contain the "configName" definition. Solr should
not be deleting anything from ZK when it starts. Only explicit user
action should delete information related to your collections.
I have no idea why Solr can't find that information. Maybe it was never
written to ZK, perhaps because of a permissions issue at the ZK level.
Maybe the *read* permissions are not correct. Maybe one or more of your
Solr servers are starting with incorrect zkHost values. Maybe your ZK
servers are having problems.
If you go to the admin UI of one of your three servers that you have not
been restarted, click on Cloud and then Tree, what do you see? If you
see a "collections" folder, open it with the little arrow/triangle.
Inside that, are there collections? If so, and you click on one, you
should see a bunch of attributes in the right-hand side, and some JSON
below those attributes.
Thanks,
Shawn
