hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5873) Shuffle bandwidth computation includes time spent waiting for maps
Date Wed, 15 Oct 2014 16:05:34 GMT

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

Jason Lowe updated MAPREDUCE-5873:
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks, Siqi!  I committed this to trunk, branch-2, and branch-2.6.

> Shuffle bandwidth computation includes time spent waiting for maps
> ------------------------------------------------------------------
>
>                 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
>             Fix For: 2.6.0
>
>         Attachments: MAPREDUCE-5873.v1.patch, MAPREDUCE-5873.v2.patch, MAPREDUCE-5873.v3.patch,
MAPREDUCE-5873.v4.patch, MAPREDUCE-5873.v5.patch, MAPREDUCE-5873.v6.patch, MAPREDUCE-5873.v9.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)

Mime
View raw message