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 2015/06/09 17:56:01 UTC

[jira] [Commented] (SPARK-8275) HistoryServer caches incomplete App UIs

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

Steve Loughran commented on SPARK-8275:
---------------------------------------

I have a test for this as part of the SPARK-1537 WiP; I haven't yet done a fix.

> HistoryServer caches incomplete App UIs
> ---------------------------------------
>
>                 Key: SPARK-8275
>                 URL: https://issues.apache.org/jira/browse/SPARK-8275
>             Project: Spark
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 1.3.1
>            Reporter: Steve Loughran
>
> The history server caches applications retrieved from the {{ApplicationHistoryProvider.getAppUI()}} call for performance: it's expensive to rebuild.
> However, this cache also includes incomplete applications, as well as completed ones —and it never attempts to refresh the incomplete application.
> As a result, if you do a GET of the history of a running application, even after the application is finished, you'll still get the web UI/history as it was when that first GET was issued.



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