hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Minho Kim (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HAMA-936) Occasional yarn job fails with timeout exception
Date Mon, 18 May 2015 05:54:59 GMT

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

Minho Kim reassigned HAMA-936:
------------------------------

    Assignee: Minho Kim  (was: Edward J. Yoon)

> Occasional yarn job fails with timeout exception
> ------------------------------------------------
>
>                 Key: HAMA-936
>                 URL: https://issues.apache.org/jira/browse/HAMA-936
>             Project: Hama
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 0.6.4
>            Reporter: Edward J. Yoon
>            Assignee: Minho Kim
>             Fix For: 0.7.0
>
>
> Reported summary: Job has finished successfully but no containers. So finally, job throws
FAILED status with timeout exception.
> What happen if the getContainerStatuses only returns the current container statuses?
In other words, if the getContainerStatuses doesn't care about the completed containers, logic
of JobImpl.startJob() implementation is very unstable.



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

Mime
View raw message