You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Siqi Li (JIRA)" <ji...@apache.org> on 2014/10/04 01:17:35 UTC

[jira] [Updated] (MAPREDUCE-5873) Measure bw of a single copy call and display the correct aggregated bw

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

Siqi Li updated MAPREDUCE-5873:
-------------------------------
    Status: Open  (was: Patch Available)

> Measure bw of a single copy call and display the correct aggregated bw
> ----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5873
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5873
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>         Attachments: MAPREDUCE-5873.v1.patch, MAPREDUCE-5873.v2.patch, MAPREDUCE-5873.v3.patch, MAPREDUCE-5873.v4.patch
>
>
> Currently ShuffleScheduler in ReduceTask JVM status displays bandwidth. Its definition however is confusing because it captures the time where there is no copying because there is a pause between when new wave of map outputs is available.
> current bw is definded as (bytes copied so far) / (total time in the copy phase so far)
> It would be more useful 
> 1) to measure bandwidth of a single copy call.
> 2) display aggregated bw as long as there is at least one fetcher is in the copy call.



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