[
https://issues.apache.org/jira/browse/SPARK-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-15844.
------------------------------------
Resolution: Fixed
Assignee: Steve Loughran
Fix Version/s: 2.2.0
> HistoryServer doesn't come up if spark.authenticate = true
> ----------------------------------------------------------
>
> Key: SPARK-15844
> URL: https://issues.apache.org/jira/browse/SPARK-15844
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.6.0
> Environment: cluster with spark.authenticate = true
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 2.2.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
