hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yufei Gu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5774) MR Job stuck in ACCEPTED status without any progress in Fair Scheduler
Date Mon, 24 Oct 2016 21:53:58 GMT

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

Yufei Gu updated YARN-5774:
---------------------------
    Description: 
MR Job stuck in ACCEPTED status without any progress in Fair Scheduler because there is no
resource request for the AM. This happened when you configure {{yarn.scheduler.minimum-allocation-mb}}
to zero.

The problem is in the code used by both Capacity Scheduler and Fair Scheduler. scheduler.increment-allocation-mb
is a concept in FS, but not CS. So the common code in class RMAppManager passes the yarn.scheduler.minimum-allocation-mb
as incremental one because there is no incremental one for CS when it tried to normalize the
resource requests.
{code}
     SchedulerUtils.normalizeRequest(amReq, scheduler.getResourceCalculator(),
          scheduler.getClusterResource(),
          scheduler.getMinimumResourceCapability(),
          scheduler.getMaximumResourceCapability(),
          scheduler.getMinimumResourceCapability());  --> incrementResource should be passed
here.
{code}

  was:
MR Job stuck in ACCEPTED status without any progress in Fair Scheduler because there is no
resource request for the AM. 

The problem is in the code used by both Capacity Scheduler and Fair Scheduler. scheduler.increment-allocation-mb
is a concept in FS, but not CS. So the common code in class RMAppManager passes the yarn.scheduler.minimum-allocation-mb
as incremental one because there is no incremental one for CS when it tried to normalize the
resource requests.
{code}
     SchedulerUtils.normalizeRequest(amReq, scheduler.getResourceCalculator(),
          scheduler.getClusterResource(),
          scheduler.getMinimumResourceCapability(),
          scheduler.getMaximumResourceCapability(),
          scheduler.getMinimumResourceCapability());  --> incrementResource should be passed
here.
{code}


> MR Job stuck in ACCEPTED status without any progress in Fair Scheduler
> ----------------------------------------------------------------------
>
>                 Key: YARN-5774
>                 URL: https://issues.apache.org/jira/browse/YARN-5774
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>
> MR Job stuck in ACCEPTED status without any progress in Fair Scheduler because there
is no resource request for the AM. This happened when you configure {{yarn.scheduler.minimum-allocation-mb}}
to zero.
> The problem is in the code used by both Capacity Scheduler and Fair Scheduler. scheduler.increment-allocation-mb
is a concept in FS, but not CS. So the common code in class RMAppManager passes the yarn.scheduler.minimum-allocation-mb
as incremental one because there is no incremental one for CS when it tried to normalize the
resource requests.
> {code}
>      SchedulerUtils.normalizeRequest(amReq, scheduler.getResourceCalculator(),
>           scheduler.getClusterResource(),
>           scheduler.getMinimumResourceCapability(),
>           scheduler.getMaximumResourceCapability(),
>           scheduler.getMinimumResourceCapability());  --> incrementResource should
be passed here.
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message