I may have been wrong about adding "/solr" to your zookeepers. I know I had to do that somewhere, but I guess it was when starting solr from the commandline without the "bin/solr start" command. So, you can re-upload your config directory to a configset named "lab". It will create or overwrite the current configset (which is just a ZK directory of your conf directory). The default configset name is the same as your collection. T ./zkcli.sh -zkhost localhost:2181 -cmd upconfig -confdir /opt/lucidworks-hdpsearch/solr/server/solr/configsets/data_driven_schema_configs_hdfs/conf -confname lab If your configset is called testcoll, then do this to show the contents of the solrconfig.xml in zookeeper: ./zkcli.sh -zkhost localhost:2181 -cmd get /configs/lab/solrconfig.xml I recommend running the list command which will dump everything in zookeeper, not just listing files but will print the contents of the files. That's a bit too much, so just pipe it to "less" and then search for your collection name as you would with vi (with / and ? to search). Then you'll see the path to your configs. ./zkcli.sh -zkhost localhost:2181 -cmd list |less you will see something like this (my collection is called testcoll in this example): /configs/testcoll/solrconfig.xml (0) DATA: ...supressed... /configs/testcoll/lang (38) /configs/testcoll/lang/contractions_ga.txt (0) DATA: ...supressed... /configs/testcoll/lang/stopwords_hi.txt (0) DATA: ...supressed... /configs/testcoll/lang/stopwords_eu.txt (0) DATA: ...supressed... /configs/testcoll/lang/stopwords_sv.txt (0) DATA: ...supressed... /configs/testcoll/lang/contractions_it.txt (0) I hope that helps. ... View more

This will upload your config directory to a configset named "testcoll". The default configset name is the same as your collection ./zkcli.sh -zkhost localhost:2181 -cmd upconfig -confdir ../../solr/configsets/data_driven_schema_configs/conf -confname testcoll. If your configset is called testcoll, then do this to show the contents of the solrconfig.xml in zookeeper: ./zkcli.sh -zkhost localhost:2181 -cmd get /configs/testcoll/solrconfig.xml I recommend running the list command which will dump everything in zookeeper, not just listing files but will print the contents of the files. That's a bit too much, so just pipe it to "less" and then search for your collection name as you would with vi (with / and ? to search). Then you'll see the path to your configs. ... View more

@Saurabh Kumar You need to add "/solr" to the end of your zookeeper host:port like this (you probably only need to list one of the zookeepers for the command) ./zkcli.sh -cmd upconfig -confdir /opt/lucidworks-hdpsearch/solr/server/solr/configsets/data_driven_schema_configs_hdfs/conf -confname labs -z m1.hdp22:2181/solr That command will upload the conf directory. I'd also suggest trying the list command ("-cmd list") to see what's in zookeeper. It has been a ehwhile since I have used it and I can't try it at the moment. ... View more

@Saurabh Kumar - Since this example is using the Sandbox zookeeper rather than embedded zk, try adding /solr to the end of your zookeeper entry in the create command like this sandbox.hortonworks.com:2181/solr. I'm not sure if that will solve the issue but when Solr runs in cloud mode with an external zookeeper it makes /solr the zookeeper root to keep it's data separate from other services. ... View more

Thanks for the info @vpoornalingam. We resolved the issue. It turns out that when we changed the path, Ambari suggested making other changes, which we mindlessly accepted. Obviously we should have paid more attention. One of the changes was to drop the embedded hbase master heap size to a much lower value. I realized this after looking at the log hbase-ams-master-<FQDN>.out rather than ambari-metrics-collector.log that I was looking at. ... View more

Awesome. Thanks. I wasn't sure if under the covers Ranger was just doing sql grants. ... View more