flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9190) YarnResourceManager sometimes does not request new Containers
Date Tue, 24 Apr 2018 02:56:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449205#comment-16449205

ASF GitHub Bot commented on FLINK-9190:

Github user sihuazhou commented on the issue:

    @GJL I also noticed that this PR can only solve part of the problem...it can only make
sure that the `TM` is registered with ResourceManager properly, but it can't make sure that
the `TM` could connection with JobManager properly...
    Is it possible that the problem you met is that the `TM` was killed before connecting
to `JM` successfully, that way `ResourceManager `can't be notified to trigger a new container
request and the `JM` can't be notified either...What do you think?

> YarnResourceManager sometimes does not request new Containers
> -------------------------------------------------------------
>                 Key: FLINK-9190
>                 URL: https://issues.apache.org/jira/browse/FLINK-9190
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination, YARN
>    Affects Versions: 1.5.0
>         Environment: Hadoop 2.8.3
> ZooKeeper 3.4.5
> Flink 71c3cd2781d36e0a03d022a38cc4503d343f7ff8
>            Reporter: Gary Yao
>            Assignee: Sihua Zhou
>            Priority: Blocker
>              Labels: flip-6
>             Fix For: 1.5.0
>         Attachments: yarn-logs
> *Description*
> The {{YarnResourceManager}} does not request new containers if {{TaskManagers}} are killed
rapidly in succession. After 5 minutes the job is restarted due to {{NoResourceAvailableException}},
and the job runs normally afterwards. I suspect that {{TaskManager}} failures are not registered
if the failure occurs before the {{TaskManager}} registers with the master. Logs are attached;
I added additional log statements to {{YarnResourceManager.onContainersCompleted}} and {{YarnResourceManager.onContainersAllocated}}.
> *Expected Behavior*
> The {{YarnResourceManager}} should recognize that the container is completed and keep
requesting new containers. The job should run as soon as resources are available. 

This message was sent by Atlassian JIRA

View raw message