You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "zhengdong (JIRA)" <ji...@apache.org> on 2017/09/01 09:28:00 UTC

[jira] [Commented] (KYLIN-2753) Job duration may become negative after the job resumed from error or paused status

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

zhengdong commented on KYLIN-2753:
----------------------------------

Hi Billy, sorry for my mistake, haven't taken into consideration the special case that jobs not really paused.
I have updated the patch file, could you please to review it?

> Job duration may become negative after the job resumed from error or paused status
> ----------------------------------------------------------------------------------
>
>                 Key: KYLIN-2753
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2753
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v2.1.0
>            Reporter: zhengdong
>            Assignee: zhengdong
>         Attachments: 0001-KYLIN-2753-Job-duration-may-become-negative-after-th.patch, KYLIN-2753-Job-duration-may-become-negative-after-th.patch, Screen Shot 2017-08-02 at 13.30.51.png, Screen Shot 2017-08-02 at 14.01.13.png
>
>
> After KYLIN-2655, we calculate the 'Interrupt time' when a job resumed from error/stopped status to give more accurate job duration time. However, when calculate the real duration time = 'Total time' - 'Interrupt time', we could get a negative value.
> The root cause is 'Interrupt time' calculated in DefaultChainedExecutable.onExecuteStart method. The 'Interrupt time' value is not only added with the true 'Interrupt time' when the job scheduled after resumed, but also increased when subsequent sub tasks executed.



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