spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From steveloughran <...@git.apache.org>
Subject [GitHub] spark pull request: [SPARK-7889] [CORE] HistoryServer to refresh c...
Date Wed, 23 Dec 2015 18:11:55 GMT
Github user steveloughran commented on a diff in the pull request:

    https://github.com/apache/spark/pull/6935#discussion_r48367142
  
    --- Diff: docs/monitoring.md ---
    @@ -69,36 +83,53 @@ follows:
       </tr>
     </table>
     
    +### Spark configuration options
    +
     <table class="table">
       <tr><th>Property Name</th><th>Default</th><th>Meaning</th></tr>
       <tr>
         <td>spark.history.provider</td>
    -    <td>org.apache.spark.deploy.history.FsHistoryProvider</td>
    +    <td><code>org.apache.spark.deploy.history.FsHistoryProvider</code></td>
         <td>Name of the class implementing the application history backend. Currently
there is only
         one implementation, provided by Spark, which looks for application logs stored in
the
         file system.</td>
       </tr>
       <tr>
    +    <td>spark.history.retainedApplications</td>
    +    <td>50</td>
    --- End diff --
    
    I'm not entirely sure why that ended up there. You could make the case for separating
fs options from other ones, but really the most important is that log dir value, as without
it: nothing else works


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


Mime
View raw message