Support Questions

Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

Wrong Ambari command order for Solr when storing indexes on HDFS

New Contributor

I have installed HDP Search 3.0 on a HDP 2.6 / Ambari 2.6 setup.

I am using SolrCloud and I store the indexes on HDFS.

In the configuration "Enable support for Solr on HDFS" is checked.

When using Ambari to stop all services in the cluster, Solr is being stopped as last service. However, it depends on ZooKeeper and HDFS. Therefore, it is not able to remove its index lock files, so the next time it won't come up unless the index lock files are first removed.

This seems like a bug to me. I know there is an option to delete the write.lock files automatically but that just hides the problem.

Is there any way to change the process start/stop order?


New Contributor

Hi Bruno,

you are right is a bug. This ambari package is created by lucidworks.

This issue we discussed here.


Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.