Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.1.0
-
None
-
None
Description
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.