Known Issues in Apache Solr
Learn about the known issues in Apache Solr, the impact or changes to the functionality, and the workaround.
Known issues identified in Cloudera Runtime 7.3.2.20000 SP2
There are no new known issues in this release.
Known issues identified in Cloudera Runtime 7.3.2.10000 SP1
There are no new known issues in this release.
Known issues identified in Cloudera Runtime 7.3.2.100 CHF 1
There are no new known issues in this release.
Known issues identified in Cloudera Runtime 7.3.2
- CDPD-125501: Solr server log files are empty after upgrading Cloudera Manager to 7.13.3
-
After upgrading to Cloudera Manager 7.13.3.0 on runtimes without the CDPD-125501 launcher fix, the Solr and Infra Solr log files are 0 bytes. The cause is that Cloudera Manager adds the
EventCatcherLog4j 2 appender when the Enable Log Event Capture property is on, and the runtime cannot load it.This issue shows up on the first restart after the upgrade. Solr health checks still pass, and diagnostic bundles contain empty logs.
- CDPD-125782: HBase batch indexer and MapReduceIndexerTool jobs fail with GraalVmProcessor not found
-
When you run an HBase batch indexer or MapReduceIndexerTool job on Cloudera Runtime 7.3.2 with Cloudera Manager 7.13.3.0 builds up to -31, the job can fail with
Provider org.apache.logging.log4j.core.config.plugins.processor.GraalVmProcessor not found. The failure occurs when the morphline contains ajava { }block.The Cloudera Manager event-publish-7.13.3-shaded.jar contains a service entry for a processor that is not available after the jar is shaded. The Cloudera Manager agent places this jar on the MapReduce task classpath. NRT indexing and Cloudera Runtime 7.3.3 are not affected.
Known issues identified before Cloudera Runtime 7.3.2
- Creating Solr collection snapshots using solrctl fails on TLS-enabled clusters
- 7.3.2 and its SPs and CHFs, 7.3.1 and its SPs and CHFs, 7.1.9 and its SPs and CHFs
