[
https://issues.apache.org/jira/browse/AMBARI-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660918#comment-14660918
]
Hudson commented on AMBARI-12284:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3240 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3240/])
AMBARI-12284. Ambari omits the line to enable kerberos on the Spark History
Service (rlevas) (rlevas:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=26812c1f9b1de079d808debb33cde3e726a94789)
* ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/kerberos.json
> Ambari omits the line to enable kerberos on the Spark History Service
> ---------------------------------------------------------------------
>
> Key: AMBARI-12284
> URL: https://issues.apache.org/jira/browse/AMBARI-12284
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Steve Loughran
> Assignee: Robert Levas
> Fix For: 2.2.0
>
> Attachments: AMBARI-12284_branch-2.1_01.patch,
> AMBARI-12284_trunk_01.patch
>
>
> Ambari omits the line to enable kerberos on the Spark History Service
> When Ambari sets up a secure spark cluster, it doesn't set
> This will still fail tests unless the line
> spark.history.kerberos.enabled true
> is added to spark-defaults.conf
> without this the Spark History Service will not log in with the keytab, and
> so not set up a long-lived secure connection to a Yarn History Server with
> encryption on.
> This isn't immediately visible (and hard to sport in the tests), because if
> the user spark has logged in with kinit, the TGT is picked up and used —which
> works until the ticket expires.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
