You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2015/06/30 15:44:04 UTC

[jira] [Commented] (SPARK-6951) History server slow startup if the event log directory is large

    [ https://issues.apache.org/jira/browse/SPARK-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608287#comment-14608287 ] 

Thomas Graves commented on SPARK-6951:
--------------------------------------

This actually happens more then just at start up.  If you have  large number of files, especially in progress files.  Or even just large history files, it takes forever for the history server to pick up new completed ones and show on the UI. 

> History server slow startup if the event log directory is large
> ---------------------------------------------------------------
>
>                 Key: SPARK-6951
>                 URL: https://issues.apache.org/jira/browse/SPARK-6951
>             Project: Spark
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 1.3.0
>            Reporter: Matt Cheah
>
> I started my history server, then navigated to the web UI where I expected to be able to view some completed applications, but the webpage was not available. It turned out that the History Server was not finished parsing all of the event logs in the event log directory that I had specified. I had accumulated a lot of event logs from months of running Spark, so it would have taken a very long time for the History Server to crunch through them all. I purged the event log directory and started from scratch, and the UI loaded immediately.
> We should have a pagination strategy or parse the directory lazily to avoid needing to wait after starting the history server.



--
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