Cloudera Docs

Known Issues in Impala

Known issues and technical limitations for Impala are addressed in Cloudera Runtime 7.1.9 SP2.

Known issues identified in Cloudera Runtime 7.1.9 SP2

CDPD-100746: Incorrect memory reservation accounting after abnormal executor termination
If an executor backend terminates abnormally, the memory reserved accounting is not updated. This causes the admission controller to maintain an incorrect view of the reserved memory for that specific backend. Even after you restart the executor and add it back to the cluster, the reserved memory remains set to the value it held before the termination. This incorrect value persists even after the associated session is closed.
None

Apache Jira: IMPALA-12146

CDPD-100741: Cancelling queries can cause lock contention on the coordinator
The coordinator holds a lock while it sends the CancelQueryFInstances RPC. This action can cause delays for other threads that require this lock. In extreme cases, this can cause the RPC framework to stall, which might result in RPC timeouts.
None

Apache Jira: IMPALA-14271

CDPD-100118: Impala select queries fail with TableLoadingException during concurrent metadata operations
Impala select queries can fail with a TableLoadingException when HMS is performing DROP partition operations on the same table at the same time.
None

Apache Jira: HIVE-28145

Known issues identified before Cloudera Runtime 7.1.9 SP2

CDPD-60862: Rolling restart fails during ZDU when DDL operations are in progress

During a Zero Downtime Upgrade (ZDU), the rolling restart of services that support Data Definition Language (DDL) statements might fail if DDL operations are in progress during the upgrade. As a result, ensure that you do not run DDL statements during ZDU.

The following services support DDL statements:
  • Impala
  • Hive – using HiveQL
  • Spark – using SparkSQL
  • HBase
  • Phoenix
  • Kafka

Data Manipulation Lanaguage (DML) statements are not impacted and can be used during ZDU. Following the successful upgrade, you can resume running DDL statements.

None. Cloudera recommends modifying applications to not use DDL statements for the duration of the upgrade. If the upgrade is already in progress, and you have experienced a service failure, you can remove the DDLs in-flight and resume the upgrade from the point of failure.
CDPD-94720: Impala startup failure due to invalid TLS v1.3 ciphers
When running Impala on a machine with OpenSSL 1.1.1, providing an invalid or TLS v1.2 ciphersuite in the --tls_ciphersuites startup flag causes the process to fail during startup. While OpenSSL 3.x ignores invalid ciphers, OpenSSL 1.1.1 returns an error if any ciphersuite in the list is invalid, even if other valid TLS v1.3 ciphers are present.
Ensure that the list in the --tls_ciphersuites startup flag contains only valid TLS v1.3 ciphersuites and does not contain any TLS v1.2 ciphersuites.

Apache Jira: IMPALA-14625

CDPD-59625: Impala shell in RHEL 9 with Python 2 as default does not work
If you try to run impala-shell on RHEL 9 by setting the default python executable available in PATH to Python 2, it will fail since RHEL 9 is compatible only with Python 3.
If you run into such issues, set this parameter pointing to Python 3, IMPALA_PYTHON_EXECUTABLE=python3.