ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <>
Subject [jira] [Commented] (AMBARI-9022) Kerberos config lost + Cluster outage after adding Kafka service or Oozie service (or any service?)
Date Thu, 12 Feb 2015 05:59:11 GMT


John Speidel commented on AMBARI-9022:

Merged fix for auth_to_local property issue.
With this patch applied I was able to successfully add Kafka to a kerberized cluster.
When trying to add oozie, oozie failed to start with "Fail: Configuration parameter 'oozie.service.HadoopAccessorService.kerberos.principal'
was not found in configurations dictionary!"

> Kerberos config lost + Cluster outage after adding Kafka service or Oozie service (or
any service?)
> ---------------------------------------------------------------------------------------------------
>                 Key: AMBARI-9022
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-server, security
>    Affects Versions: 1.7.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Assignee: Rishi Pidva
>            Priority: Blocker
> Adding the Kafka service to an existing kerberized HDP 2.2 cluster resulted in all the
Kerberos fields in core-site.xml getting blank or literal "null" string which prevented all
the HDFS and Yarn instances from restarting. This caused a major outage - lucky this cluster
isn't prod but this is going to bite somebody badly.
> Error observed in NameNode log:
> {code}2015-01-07 09:56:01,958 INFO  namenode.NameNode (
- Clients are to use nameservice1 to access this namenode/service.
> 2015-01-07 09:56:02,055 FATAL namenode.NameNode ( - Failed to
start namenode.
> java.lang.IllegalArgumentException: Invalid rule: null
>         at
>         at
>         at
>         at
>         at
>         at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(
>         at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(
>         at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(
>         at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(
>         at org.apache.hadoop.hdfs.server.namenode.NameNode.main(
> 2015-01-07 09:56:02,062 INFO  util.ExitUtil ( - Exiting
with status 1
> 2015-01-07 09:56:02,064 INFO  namenode.NameNode ( - SHUTDOWN_MSG:{code}
> Fields which ended up being with "null" string literals in the value field in core-site.xml:
> hadoop.http.authentication.kerberos.principal
> Fields which ended up being blank ("") for value field in core-site.xml:
> {code}hadoop.http.authentication.cookie.domain
> hadoop.http.authentication.cookie.path
> hadoop.http.authentication.signature.secret
> hadoop.http.authentication.signature.secret.file
> hadoop.http.authentication.signer.secret.provider
> hadoop.http.authentication.signer.secret.provider.object
> hadoop.http.authentication.token.validity
> hadoop.http.filter.initializers{code}
> Previous revisions showed undefined which was definitely not the case for past months
this was a working fully kerberized cluster.
> Removing the Kafka service via rest API calls and restarting ambari-server didn't make
the config reappear either.
> I had to de-kerberize cluster and re-kerberize the whole cluster in Ambari in order to
get all those 12 configuration settings re-populated.
> A remaining side effect of this bug even after recovering the cluster is that all the
previous config revisions are now ruined due to the many undefined values that would prevent
the cluster from starting and are therefore no longer viable as a backup to revert to for
any reason. There doesn't seem to be much I can workaround that.
> Ironically the kafka brokers started up fine after ruining all the core components since
Kafka has no security itself.
> Regards,
> Hari Sekhon

This message was sent by Atlassian JIRA

View raw message