[
https://issues.apache.org/jira/browse/SPARK-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322793#comment-15322793
]
Apache Spark commented on SPARK-15844:
--------------------------------------
User 'steveloughran' has created a pull request for this issue:
https://github.com/apache/spark/pull/13579
> 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
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
