You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/02/10 02:32:35 UTC

[jira] [Commented] (SPARK-5703) AllJobsPage throws empty.max error

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

Apache Spark commented on SPARK-5703:
-------------------------------------

User 'andrewor14' has created a pull request for this issue:
https://github.com/apache/spark/pull/4490

> AllJobsPage throws empty.max error
> ----------------------------------
>
>                 Key: SPARK-5703
>                 URL: https://issues.apache.org/jira/browse/SPARK-5703
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.2.0
>            Reporter: Andrew Or
>            Assignee: Andrew Or
>            Priority: Critical
>
> In JobProgressListener, if you have a JobEnd that does not have a corresponding JobStart, AND you render the AllJobsPage, then you'll run into the empty.max exception.
> I ran into this when trying to replay parts of an event log after trimming a few events. Not a common use case I agree, but I'd argue that it should never fail on empty.max.



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