Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Wrong Ambari command order for Solr when storing indexes on HDFS

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?

1 REPLY 1
Highlighted

Re: Wrong Ambari command order for Solr when storing indexes on HDFS

New Contributor

Hi Bruno,

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

This issue we discussed here.

Best

Don't have an account?
Coming from Hortonworks? Activate your account here