hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chang Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4218) Metric for resource*time that was preempted
Date Tue, 06 Oct 2015 21:25:26 GMT

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

Chang Li updated YARN-4218:
    Attachment: YARN-4218.2.patch

> 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
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: YARN-4218.2.patch, YARN-4218.2.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

View raw message