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
There are no new known issues identified in this release.
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
- When you run the solrctl command to create a
collection snapshot (such as
solrctl collection --create-snapshot) on a
cluster with TLS and Kerberos enabled, the command fails with an
IOException occurred when talking to server at: error
message.This issue occurs because the TLS truststore location and password are not
exported in the shell environment, preventing the solrctl client from
establishing a secure connection to the Apache Solr server over HTTPS. Using the Solr
REST API directly to create or list snapshots is not affected.
- To resolve this issue, export the truststore path and
password in the JAVA_TOOL_OPTIONS environment variable before you run
the solrctl command:
JAVA_TOOL_OPTIONS
=
"-Djavax.net.ssl.trustStore=[***PATH_TO_TRUSTSTORE_FILE***] -Djavax.net.ssl.trustStorePassword=[***TRUSTSTORE_PASSWORD***]"
After setting the environment variable, run the
solrctl command:
solrctl --jaas
[
***PATH_TO_JAAS_CONF***
]
collection --create-snapshot
[
***SNAPSHOT_NAME***
]
-c
[
***COLLECTION_NAME***
]
