On 2/5/2018 5:13 AM, A.Guptar wrote:
> We are having issues with SolrCloud 5.4.1 instances after the hosting
> servers have been restarted.
>
> Scenario:
> We have 3 servers, on which SolrCloud 5.4.1 was configured and setup to be
> used with an external ZooKeeper ensemble.
> Once configured and setup, it works fine until there is a full server
> restart.
> The error "No config data found at path xxx" is obtained.
> As a workaround, we stopped the ZooKeeper and SolrCloud services and deleted
> all the relevant data before re-creating everything from scratch.
>
> I use the following commands for creating the config and collections in ZK
> and SolrCloud.
>
> function UploadZooKeeperConfig {
> ...
> Start-Process -FilePath ${zkCliPath}\${zkcli} -ArgumentList "-zkhost
> ${zkHost}:${zkPort} -cmd upconfig -confdir ${configPath} -confname
> $confName"
> ...
> }
>
> UploadZooKeeperConfig -configPath "D:\basic_configs\conf" -confName
> "TestCollectionConfig" -zkHost "x.x.x.x"
>
> $expression =
> "http://localhost:8983/solr/admin/collections?action=CREATE&name=TestCollection&numShards=1&replicationFactor=3&collection.configName=TestCollectionConfig";
>
> Invoke-WebRequest -Uri $expression
>
> The following command is used to start SolrCloud.
>
> bin\solr start -cloud -z "xxx:2181,yyy:2181,zzz:2181" -m 16g -fThat all looks reasonable. I don't know what language your collection build script is written in, but I'm going to assume that the syntax is correct for that language. > Below is the zoo.cfg used within SolrCloud. If you are using an external ZK ensemble, then the zoo.cfg for the embedded ZK is not going to be used. So if that zoo.cfg file is part of your Solr install, it's probably not being used. The zookeeper config on your ZK servers is what's going to be important. If that's what this is, then I think it's probably OK, but I'm not a ZK expert. You should remove the "-cloud" option from the Solr startup, just to be absolutely sure that you are not starting the embedded ZK. The -z option is enough to start in SolrCloud mode. Can you provide the entire solr.log file from a startup that shows the error? If you absolutely need to redact sensitive information from the logfile, do so. I don't think there is normally much in the log that is really sensitive. If you have changed the default logging level away from INFO, please set it back to INFO before performing the restart. Thanks, Shawn
