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 MARCH 01, 2017

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 and later
Linux x86-64

Symptoms

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    

  

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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms