Lucidworks

Lucidworks Documentation

Home

Installation Issues

Installation Issues

Kerberos Issues

SIMPLE Authentication is not enabled

Problem

After Kerberos authentication is enabled, Solr commands fail with an error such as:

Caused by: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS]
Solution

There is likely something wrong with the Kerberos configuration. There are several things to check:

  • Review the Solr documentation for Kerberos at https://cwiki.apache.org/confluence/display/solr/Kerberos+Authentication+Plugin

  • Verify Kerberos-related startup parameters are being passed at startup, either with the bin/solr start command or because they exist in solr.in.sh.

  • Verify the JAAS file is properly configured, particularly the service principal.

  • Verify ZooKeeper Kerberos settings are properly configured.

Connector Issues

General Issues

Hadoop Job Jar

Hive SerDe

HBase-Indexer

Solr Issues

Startup

Solr won’t start due to index lock errors

Problem

Solr startup fails because of errors similar to:

collection_replica1: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Index locked for write for core collection_replica1

The issue is that Solr locks the index to prevent other processes from writing to the index while indexing is occurring. The files that indicate the index lock are occasionally left behind, especially if Solr processes were killed or stopped improperly.

Solution

Delete any write.lock files found in the Solr index directories (Solr’s dataDir, which is by default /etc/solr/data_dir) manually. With HDP 2.5.x, Ambari includes a script that will automatically remove any write.lock files on startup if you decide to let it. If you are not using Ambari, you will need to remove these lock files on every Solr node.

Timeouts and Performance

Shard goes into recovery

Check commit settings

Check time settings