Github user andrewor14 commented on a diff in the pull request:

    https://github.com/apache/spark/pull/718#discussion_r13618519
  
    --- Diff: 
core/src/main/scala/org/apache/spark/deploy/history/HistoryServerArguments.scala
 ---
    @@ -67,10 +69,29 @@ private[spark] class HistoryServerArguments(args: 
Array[String]) {
     
       private def printUsageAndExit(exitCode: Int) {
         System.err.println(
    -      "Usage: HistoryServer [options]\n" +
    -      "\n" +
    -      "Options:\n" +
    -      "  -d DIR,  --dir DIR     Location of event log files")
    +      """
    +      |Usage: HistoryServer [-d logDir]
    +      |
    +      |The preferred way to pass options is to set the configuration below 
using
    +      |SPARK_HISTORY_OPTS. The "-d" command line argument is avalable for 
backwards
    +      |compatibility, and overrides "spark.history.fs.logDirectory".
    +      |
    +      |History Server options are always available; additional options 
depend on the provider.
    +      |
    +      |History Server options:
    +      |
    +      |  spark.history.ui.port      Port where server will listen for 
connections (default 18080)
    +      |  spark.history.acls.enable  Whether to enable view acls for all 
applications (default false)
    +      |  spark.history.provider     Name of history provider class 
(defaults to file system-based
    +      |                             provider)
    +      |
    +      |FsHistoryProvider options:
    +      |
    +      |  spark.history.fs.logDirectory    Directory where app logs are 
stored (required)
    --- End diff --
    
    This is technically not required, as in the user can pass this through the 
--dir option rather than through `spark.history.fs.logDirectory`.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to