You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/06/09 15:52:20 UTC

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

Steve Loughran created SPARK-15844:
--------------------------------------

             Summary: 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org