Hi @Tony Bolt Did you increase the "sleep time"? Increase the sleep time from 5 to 30 seconds in /opt/lucidworks-hdpsearch/solr/bin/solr sed -i 's/(sleep 5)/(sleep 30)/g'/opt/lucidworks-hdpsearch/solr/bin/solr Since all Solr data will be stored in the Hadoop Filesystem, it is important to adjust the time Solr will take to shutdown or "kill" the Solr process (whenever you execute "service solr stop/restart"). If this setting is not adjusted, Solr will try to shutdown the Solr process and because it takes a bit more time when using HDFS, Solr will simply kill the process and most of the time lock the Solr Indexes of your collections. If the index of a collection is locked the following exception is shown after the startup routine "org.apache.solr.common.SolrException: Index locked for write" Original article can be found here => https://community.hortonworks.com/articles/15159/securing-solr-collections-with-ranger-kerberos.html ... View more

Hi @Tony Bolt how does the <DirectoryFactory> element in your solrconfig.xml look like? Just to make sure, you have uploaded the configuration to the Solr Zookeeper ZNode? Did you try to remove the Collection and all its core folders and try again? Maybe the write.lock is from a previous test and the folders havent been removed properly ... View more

@Raf Mohammed It looks like your transaction log has some issue and is preventing solr from opening a new searcher. Have you tried to restart solr or issue a manual commit ? Is your HDFS healthy? You could remove the recent transaction logs, which should resolve this issue, however you will loose the most recent ingested data. Got a checksum exception for /solr/tweets/core_node1/data/tlog/tlog.0000000000000000338 at BP-1464254149-172.17.0.2-1477381671113:blk_1073759482_18761:1024 from xxxxxxxxx:50010\cell \row . ... View more

great article.thanks 🙂 ... View more

@Hoang Le If you have 5 nodes, you can use 2 nodes as Masternodes and 3 as Workernodes (slave nodes). ... View more

@Amod Gehlot It looks like you have a problem with your SolrCloud Zookeeper configuration. Overseer cannot talk to ZK Are you storing your Solr Index in HDFS or on local disks? Could you please check your solrcloud configuration especially the ZK Quorum and maybe post the configuration files (solrconfig.xml of the collection, solr.in.sh of your solr cloud) Is this a secured environment? ... View more

@Fang Heart In order to test the connection between the Ranger Solr Plugin and the Ranger service, you can login to the Ranger Admin UI and go to Audit -> Plugins. This will show a list of synchronizations between the Ranger Plugin and Ranger service. You can also check /etc/ranger/<repository name>/policycache/.... and check the timestamp of the policycache json. ... View more

@Fang Heart 1.I think you can use Ranger Solr Plugin without Kerberos, however kerberos provides the authentication layer and therefore an additional layer of security. 2.Solr itself runs under the solr user, however the users that are allowed to access and manage your solr collections is totally up to you. You can define separate policies for each Solr Collection in Ranger and assign permissions to groups or users 3.Usually, I configure my Solr instances in a way that allows me to use "service solr start" to start my solr cloud. In order to make this work, you have to make sure ZK_HOST is defined in your solr config (solr.in.sh) ... View more