hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yiqun Lin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4396) Log the trace information on FSAppAttempt#assignContainer
Date Fri, 28 Oct 2016 05:22:58 GMT

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

Yiqun Lin updated YARN-4396:
    Summary: Log the trace information on FSAppAttempt#assignContainer  (was: Log the trance
information on FSAppAttempt#assignContainer)

> Log the trace information on FSAppAttempt#assignContainer
> ---------------------------------------------------------
>                 Key: YARN-4396
>                 URL: https://issues.apache.org/jira/browse/YARN-4396
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: applications, fairscheduler
>    Affects Versions: 2.7.1
>            Reporter: Yiqun Lin
>            Assignee: Yiqun Lin
>              Labels: oct16-easy
>         Attachments: YARN-4396.001.patch, YARN-4396.002.patch, YARN-4396.003.patch, YARN-4396.004.patch,
> When I configure the yarn.scheduler.fair.locality.threshold.node and yarn.scheduler.fair.locality.threshold.rack
to open this function, I have no detail info of assigning container's locality. And it's important
because it will lead some delay scheduling and will have an influence on my cluster. If I
know these info, I can adjust param in cluster.

This message was sent by Atlassian JIRA

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

View raw message