hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4218) Metric for resource*time that was preempted
Date Sun, 30 Oct 2016 05:39:58 GMT

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

Hadoop QA commented on YARN-4218:

| (x) *{color:red}-1 overall{color}* |
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} | {color:red}
YARN-4218 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-4218 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12836007/YARN-4218.4.patch
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/13675/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |

This message was automatically generated.

> Metric for resource*time that was preempted
> -------------------------------------------
>                 Key: YARN-4218
>                 URL: https://issues.apache.org/jira/browse/YARN-4218
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: YARN-4218.2.patch, YARN-4218.2.patch, YARN-4218.2.patch, YARN-4218.2.patch,
YARN-4218.3.patch, YARN-4218.4.patch, YARN-4218.patch, YARN-4218.wip.patch, screenshot-1.png,
screenshot-2.png, screenshot-3.png
> After YARN-415 we have the ability to track the resource*time footprint of a job and
preemption metrics shows how many containers were preempted on a job. However we don't have
a metric showing the resource*time footprint cost of preemption. In other words, we know how
many containers were preempted but we don't have a good measure of how much work was lost
as a result of preemption.
> We should add this metric so we can analyze how much work preemption is costing on a
grid and better track which jobs were heavily impacted by it. A job that has 100 containers
preempted that only lasted a minute each and were very small is going to be less impacted
than a job that only lost a single container but that container was huge and had been running
for 3 days.

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