[SPARK-15844] HistoryServer doesn't come up if spark.authenticate = true

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.6.0
• Fix Version/s: 2.2.0
• Component/s: Spark Core

Environment

cluster with spark.authenticate = true

• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 09/Jun/16 15:51
• Updated: 12/Dec/16 20:25
• Resolved: 12/Dec/16 20:25

Description

If the configuration used to start the history server has spark.authenticate set, then the server doesn't come up: there's no secret for the SecurityManager. —even though that secret is used for the secure shuffle, which the history server doesn't go anywhere near

Issue Links

• links to: [Github] Pull Request #13579 (steveloughran)