hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1018) Document changes to the memory management and scheduling model
Date Tue, 01 Jun 2010 00:15:40 GMT

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

Tom White commented on MAPREDUCE-1018:
--------------------------------------

Hemanth, This is going to conflict with MAPREDUCE-1404, which moves cluster setup and commands
manual pages to common. Would you be able to stage this one to go in after MAPREDUCE-1404?

bq. One thing I've not included is the documentation on the RSS based monitoring introduced
in MAPREDUCE-1221. I am not yet familiar with that part of the code. Also, this patch itself
looks reasonably big. Hence, I would request for those changes to be incorporated as a follow-up,
though they should be treated as a blocker for the 0.21 release as well. Thoughts ?

Fine to have as a separate issue, but I don't think it would stop a release going out (we
could add it in a point release if it didn't make it into the .0 release).

> Document changes to the memory management and scheduling model
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-1018
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1018
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.21.0
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: MAPRED-1018-1.patch, MAPRED-1018-2.patch, MAPRED-1018-3.patch, MAPRED-1018-4.patch.txt,
MAPRED-1018-5.patch.txt, MAPRED-1018-6.patch.txt, MAPRED-1018-7.patch.txt, MAPRED-1018-commons.patch
>
>
> There were changes done for the configuration, monitoring and scheduling of high ram
jobs. This must be documented in the mapred-defaults.xml and also on forrest documentation

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message