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

Marcelo Vanzin edited comment on SPARK-18085 at 9/1/17 6:37 PM:
----------------------------------------------------------------

[~jincheng] do you have code that can reproduce that? The code in the exception 
hasn't really changed, so this is probably an artifact of how the new code is 
recording data from the application. From your description (when we clicking 
stages with no tasks successful) I haven't been able to reproduce this; a stage 
that has only failed tasks still renders fine with the code in my branch.


was (Author: vanzin):
[~jincheng] do you have code that can reproduce that? The code in the exception 
hasn't really changed, so this is probably an artifact of how the new code is 
recording data from the application. For your description (when we clicking 
stages with no tasks successful) I haven't been able to reproduce this; a stage 
that has only failed tasks still renders fine with the code in my branch.

> SPIP: Better History Server scalability for many / large applications
> ---------------------------------------------------------------------
>
>                 Key: SPARK-18085
>                 URL: https://issues.apache.org/jira/browse/SPARK-18085
>             Project: Spark
>          Issue Type: Umbrella
>          Components: Spark Core, Web UI
>    Affects Versions: 2.0.0
>            Reporter: Marcelo Vanzin
>              Labels: SPIP
>         Attachments: spark_hs_next_gen.pdf
>
>
> It's a known fact that the History Server currently has some annoying issues 
> when serving lots of applications, and when serving large applications.
> I'm filing this umbrella to track work related to addressing those issues. 
> I'll be attaching a document shortly describing the issues and suggesting a 
> path to how to solve them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to