Critical Description
Oozie server fails to start with the error: "Fail: Configuration parameter 'oozie.service.HadoopAccessorService.kerberos.principal' was not found in configurations dictionary!"
Steps to reproduce:
Create a non-kerberized cluster
I used the following blueprint
{
"host_groups" : [
{
"name" : "host_group_1",
"components" : [
{
"name" : "NODEMANAGER"
},
{
"name" : "NAMENODE"
},
{
"name" : "HISTORYSERVER"
},
{
"name" : "ZOOKEEPER_SERVER"
},
{
"name" : "SECONDARY_NAMENODE"
},
{
"name" : "RESOURCEMANAGER"
},
{
"name" : "APP_TIMELINE_SERVER"
},
{
"name" : "DATANODE"
},
{
"name" : "YARN_CLIENT"
},
{
"name" : "ZOOKEEPER_CLIENT"
},
{
"name" : "MAPREDUCE2_CLIENT"
}
],
"cardinality" : "1"
}
],
"Blueprints" : {
"stack_name" : "HDP",
"stack_version" : "2.2"
}
}
- manually unzip UnlimitedJCEPolicy
- manually install MIT KDC
- Using UI, kerberize the existing cluster
- Using the UI, add the Oozie service
OOZIE_SERVER failed to start and the above noted exception was from the log that is exposed via the UI for the oozie start operation.
According to Robert Levas this property is in the kerberos descriptor it should be set.