Known Issues in Cloudera Search
Learn about the known issues in Cloudera Search, the impact or changes to the functionality, and the workaround.
- DOCS-5717: Lucene index handling limitation
- The Lucene index can only be upgraded by one major version. Solr 8 will not open an index that was created with Solr 6 or earlier.
- None, you need to reindex collections.
- CDH-82042: Solr service with no added collections causes the upgrade process to fail.
- Upgrade fails while performing the bootstrap collections step of the
solr-upgrade.shscript with the error message:
if there are no collections present in Solr.
Failed to execute command Bootstrap Solr Collections on service Solr
- If there are no collections added to it, remove the Solr service from your cluster before you start the upgrade.
- CDH-34050: Collection Creation No Longer Supports Automatically Selecting A Configuration If Only One Exists.
- Before CDH 5.5.0, a collection could be created without specifying a configuration.
-cvalue was specified, then:
If there was only one configuration, that configuration was chosen.
If the collection name matched a configuration name, that configuration was chosen.
Search now includes multiple built-in configurations. As a result, there is no longer a case in which only one configuration can be chosen by default.
- Explicitly specify the collection configuration to use by passing
solrctl collection --create.
- CDH-22190: CrunchIndexerTool which includes Spark indexer requires specific input file format specifications.
- If the
--input-file-formatoption is specified with CrunchIndexerTool, then its argument must be
avroParquet, rather than a fully qualified class name.
- CDH-19923: he
quickstart.shfile does not validate ZooKeeper and the NameNode on some operating systems.
quickstart.shfile uses the
timeoutfunction to determine if ZooKeeper and the NameNode are available. To ensure this check can be complete as intended, the
quickstart.shdetermines if the operating system on which the script is running supports
timeout. If the script detects that the operating system does not support
timeout, the script continues without checking if the NameNode and ZooKeeper are available. If your environment is configured properly or you are using an operating system that supports
timeout, this issue does not apply.
- This issue only occurs in some operating systems. If
timeoutis not available, the quickstart continues and final validation is always done by the MapReduce jobs and Solr commands that are run by the quickstart.
- CDH-26856: ield value class guessing and Automatic schema field addition are not supported with the MapReduceIndexerTool nor with the HBaseMapReduceIndexerTool.
- The MapReduceIndexerTool and the HBaseMapReduceIndexerTool can be used with a Managed Schema created via NRT indexing of documents or via the Solr Schema API. However, neither tool supports adding fields automatically to the schema during ingest.
- Define the schema before running the MapReduceIndexerTool or
HBaseMapReduceIndexerTool. In non-schemaless mode, define in the schema using the
schema.xmlfile. In schemaless mode, either define the schema using the Solr Schema API or index sample documents using NRT indexing before invoking the tools. In either case, Cloudera recommends that you verify that the schema is what you expect, using the List Fields API command.
- CDH-19407: The Browse and Spell Request Handlers are not enabled in schemaless mode.
- The Browse and Spell Request Handlers require certain fields to be present in the schema. Since those fields cannot be guaranteed to exist in a Schemaless setup, the Browse and Spell Request Handlers are not enabled by default.
- If you require the Browse and Spell Request Handlers, add them to the
solrconfig.xmlconfiguration file. Generate a non-schemaless configuration to see the usual settings and modify the required fields to fit your schema.
- CDH-17978: Enabling blockcache writing may result in unusable indexes.
- It is possible to create indexes with
true. Such indexes may appear corrupt to readers, and reading these indexes may irrecoverably corrupt indexes. Blockcache writing is disabled by default.
- CDH-58276: Users with insufficient Solr permissions may receive a "Page Loading" message from the Solr Web Admin UI.
- Users who are not authorized to use the Solr Admin UI are not given a page explaining that access is denied to them, instead receive a web page that never finishes loading.
- CDH-15441: Using MapReduceIndexerTool or HBaseMapReduceIndexerTool multiple times may produce duplicate entries in a collection
- Repeatedly running the MapReduceIndexerTool on the same set of input files can result in duplicate entries in the Solr collection. This occurs because the tool can only insert documents and cannot update or delete existing Solr documents. This issue does not apply to the HBaseMapReduceIndexerTool unless it is run with more than zero reducers.
- To avoid this issue, use HBaseMapReduceIndexerTool with zero reducers. This must be done without Kerberos.
- CDH-58694: Deleting collections might fail if hosts are unavailable.
- It is possible to delete a collection when hosts that host some of the collection are unavailable. After such a deletion, if the previously unavailable hosts are brought back online, the deleted collection may be restored.
- Ensure all hosts are online before deleting collections.
- CCDPD-4139: Collection state goes down after Solr SSL.
- If you enable TLS/SSL on a Solr instance with existing collections, the collections will break and become unavailable. Collections created after enabling TLS/SSL are not affected by this issue.
- Recreate the collection after enabling TLS.
- CDPD-13923: Every Configset is Untrusted Without Kerberos
- Solr 8 introduces the concept of ‘untrusted configset’, denoting configsets that were uploaded without authentication. Collections created with an untrusted configset will not initialize if <lib> directives are used in the configset.
- Select one of the following options if you would like to use untrusted configsets with
If the configset contains external libraries, but you do not want to use them, simply upload the configsets after deleting the <lib> directives.
If the configset contains external libraries, and you want to use them, choose one from the following options:
Secure your cluster before reuploading the configset.
Add the libraries to Solr’s classpath, then reupload the configset without the <lib> directives.
- Package Management System
- Solr SQL/JDBC
- Graph Traversal
- Cross Data Center Replication (CDCR)
- SolrCloud Autoscaling
- HDFS Federation
- Saving search results
- Solr contrib modules (Spark, MapReduce and Lily HBase indexers are not contrib modules but part of the Cloudera Search product itself, therefore they are supported).
- Default Solr core names cannot be changed
- Although it is technically possible to give user-defined Solr core names during core creation, it is to be avoided in te context of Cloudera Search. Cloudera Manager expects core names in the default "collection_shardX_replicaY" format. Altering core names results in Cloudera Manager being unable to fetch Solr metrics for the given core and this, eventually, may corrupt data collection for co-located core, or even shard and server level charts.