ADH known issues
| Service/component | Issue | From | Fixed | Workaround | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
Ozone |
There is no option to enable Kerberos authentication after installation |
3.3.6.2 |
— |
You must first install a cluster without a service, enable SSL and Kerberos, and then install and configure the Ozone service |
||||||
Ozone |
Clients do not work when secure intercomponent communication is enabled. Do not enable |
3.3.6.2 |
— |
— |
||||||
Trino, Smart Storage Manager |
The Trino service does not currently support the SSM client. This means that when Enable SmartFileSystem for Hadoop (an SSM configuration parameter) is enabled, Trino will not work |
3.3.6.2 |
— |
Do not enable SmartFileSystem for Hadoop if Trino is used |
||||||
Flink and YARN HA |
If YARN high availability is enabled (YARN has multiple ResourceManager components), certain configuration parameters have to be specified manually to allow proper interaction between Flink and highly available YARN |
4.0.0 |
4.1.0 |
As a temporary workaround, the following parameters must be specified in ADCM Flink settings (Clusters → <ADH_cluster> → Services → Flink → Primary configuration → Custom flink-conf.yaml):
The up-to-date value for
Sample output: <name>yarn.resourcemanager.ha.rm-ids</name> <value>rm_ka-adh-2,rm_ka-adh-3</value> |
||||||
Impala |
The problem is the integration of Impala with external object storage. During configuration and table creation in an S3 location, the following error occurs: |
3.3.6.2 |
4.1.0 |
Delete or transfer the following files: /usr/lib/impala/lib/aws-java-sdk-core-1.12.765.jar, /usr/lib/impala/lib/aws-java-sdk-logs-1.12.765.jar |
||||||
Trino, Ozone |
Trino does not work with Ozone using the |
3.3.6.2 |
4.0.0 |
|
||||||
Impala |
When transferring the Impala client to another host, all the necessary files are not created |
3.3.6.1 |
4.0.0 |
Restart the service after migrating components |
||||||
Smart Storage Manager |
When you enable SSL on a cluster using the Manage SSL cluster action, the service will continue to work over HTTP |
3.3.6.1 |
4.0.0 |
Manual configuration is required according to the instructions |