hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5311) Replace SLOTS_MILLIS counters with MEM_MILLIS
Date Tue, 13 Aug 2013 23:57:51 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739043#comment-13739043
] 

Alejandro Abdelnur commented on MAPREDUCE-5311:
-----------------------------------------------

[~jlowe], thanks for jumping in, I was no aware you guys have in-house tools using this stuff
with the current reported SLOT_MILLIS. With that in mind, and along the lines of what Jason
proposes would the following satisfy all parties?

This JIRA would then be repurposed to:

* Introduce and deprecate a {{MRConf.SLOT_MILLIS_MINIMUM_ALLOCATION_MB}} with no default
* If set, use the {{MRConf.SLOT_MILLIS_MINIMUM_ALLOCATION_MB}} value to compute, using today's
logic, the SLOT_MILLIS counter values.
* If no set, SLOT_MILLIS counter should report 0.

This means than anybody relying on current SLOT_MILLIS reporting can continue getting it until
we decide to trash it (a few versions down the road).

A different JIRA would introduce MEM_MILLIS and CPU_MILLIS which have an accurate meaning
in Yarn's world.

YARN-1004 is then unblocked.

I believe this address the problem without breaking backwards compatibility as [~acmurthy]
asked.

Arun, Jason, [~sandyr], are you OK with this approach?


                
> Replace SLOTS_MILLIS counters with MEM_MILLIS
> ---------------------------------------------
>
>                 Key: MAPREDUCE-5311
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5311
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster
>    Affects Versions: 2.0.4-alpha
>            Reporter: Alejandro Abdelnur
>            Assignee: Sandy Ryza
>            Priority: Blocker
>             Fix For: 2.1.0-beta
>
>         Attachments: MAPREDUCE-5311-1.patch, MAPREDUCE-5311.patch, MAPREDUCE-5311.patch
>
>
> Per discussion in MAPREDUCE-5310 and comments in the code we should remove all the related
logic and just leave the counter constant for backwards compatibility and deprecate the counter
constants.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message