On a Secure Cluster After Install / Upgrade to Mammoth V4.1.0/CDH 5.3.2 or Mammoth 4.2.0/CDH 5.4.0 When Running 'mammoth -c' Seeing"ERROR hdfs.KeyProviderCache: Could not find uri with key [dfs.encryption.key.provider.uri] to create a keyProvider !!"
(Doc ID 2017493.1)
Last updated on AUGUST 03, 2021
Applies to:
Big Data Appliance Integrated Software - Version 4.2.0 and laterLinux x86-64
Symptoms
NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.
On a secure (Kerberized) cluster after upgrading to Mammoth V4.1.0/CDH 5.3.2 or install or upgrade to Mammoth 4.2.0/CDH 5.4.0 when running 'mammoth -c' some of the jobs show failed/killed with message like:
0000002-150530035659499-oozie-oozi-W@hive-node ERROR job_1432979797467_0027 FAILED/KILLED2
------------------------------------------------------------------------------------------------------------------------------------
0000002-150530035659499-oozie-oozi-W@fail OK - OK E0729
------------------------------------------------------------------------------------------------------------------------------------
0000002-150530035659499-oozie-oozi-W@fail OK - OK E0729
In the oozie log we found errors like this from running 'mammoth -c' see messages like:
"ERROR hdfs.KeyProviderCache: Could not find uri with key [dfs.encryption.key.provider.uri] to create a keyProvider !! "
The error may also be seen on Perfect Balance jobs or when running hadoop jobs.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |