You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2016/07/28 06:49:22 UTC

[jira] [Closed] (KYLIN-1738) MRJob Id is not saved to kylin jobs if MR job is killed

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

Shaofeng SHI closed KYLIN-1738.
-------------------------------

Resolved in release 1.5.3 (2-16-07-28)

> MRJob Id is not saved to kylin jobs if MR job is killed
> -------------------------------------------------------
>
>                 Key: KYLIN-1738
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1738
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine
>    Affects Versions: v1.5.1
>            Reporter: Dong Li
>            Assignee: Dong Li
>            Priority: Minor
>             Fix For: v1.5.3
>
>
> A kylin job failed with message: killed by admin, and cannot find mr job id.
> Go through job history server, found the mr job got killed with:
> MAP capability required is more than the supported max container capability in the cluster. Killing the Job. mapResourceRequest: <memory:3072, vCores:1> maxContainerCapability:<memory:2250, vCores:32>
> Job received Kill while in RUNNING state.
> We should save the JobId for diagnosis when job status is killed like failed/finished.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)