You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/06/23 22:54:27 UTC

[jira] [Resolved] (SPARK-1768) History Server enhancements

     [ https://issues.apache.org/jira/browse/SPARK-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell resolved SPARK-1768.
------------------------------------

    Resolution: Fixed

Issue resolved by pull request 718
[https://github.com/apache/spark/pull/718]

> History Server enhancements
> ---------------------------
>
>                 Key: SPARK-1768
>                 URL: https://issues.apache.org/jira/browse/SPARK-1768
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.0.0
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>             Fix For: 1.1.0
>
>
> The history server currently has some limitations; the one that currently concerns me the most is that it limits the number of applications it will show, to avoid having to hold all applications in memory.
> It would be better if the code were smarter and able to show any application available in the history storage.
> Also, thinking forward a little bit (I'm thinking SPARK-1537), it would be nice to separate the serving logic from the logic to access app log data.



--
This message was sent by Atlassian JIRA
(v6.2#6252)