[
https://issues.apache.org/jira/browse/SPARK-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322774#comment-15322774
]
Steve Loughran commented on SPARK-15844:
----------------------------------------
Stack.
{code}
16/05/31 22:46:25 INFO SecurityManager: Changing view acls to: spark
16/05/31 22:46:25 INFO SecurityManager: Changing modify acls to: spark
Exception in thread "main" java.lang.IllegalArgumentException: Error: a secret
key must be specified via the spark.authenticate.secret config
at
org.apache.spark.SecurityManager.generateSecretKey(SecurityManager.scala:397)
at org.apache.spark.SecurityManager.<init>(SecurityManager.scala:219)
at
org.apache.spark.deploy.history.HistoryServer$.main(HistoryServer.scala:250)
at
org.apache.spark.deploy.history.HistoryServer.main(HistoryServer.scala)
{code}
> 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: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
