[ 
https://issues.apache.org/jira/browse/HADOOP-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713425#action_12713425
 ] 

Hemanth Yamijala commented on HADOOP-5881:
------------------------------------------

I had a chat with Owen regarding the objections raised.

bq. I'm concerned that this went in without an opportunity for review. The 
patch was uploaded at 5:49am and committed at 6:36am.

I apologize for the rushed commit and take responsibility. However, as I 
explained above I had reviewed the patch for a significant time. The first 
version which I reviewed is not on JIRA. In retrospect, I think that was a 
mistake, and will avoid repeating it in future. Sorry !

bq. I'm also concerned that this incompatibly changes the config variables in 
the 0.20 branch. What is the rationale for pushing these configuration changes 
back to 0.20? If they are required, they need a compatability story.

There was a misunderstanding on this point. It seemed like in an internal 
discussion we agreed to this approach. However, we are reverting stand after 
rethinking. I opened HADOOP-5919 to discuss and provide a backwards 
compatibility story for this feature. Let's keep the discussion there.

Based on these explanations, can I resolve this bug ?

> Simplify configuration related to task-memory-monitoring and memory-based 
> scheduling
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5881
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5881
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>             Fix For: 0.20.1
>
>         Attachments: HADOOP-5881-20090526-branch-20.1.txt, 
> HADOOP-5881-20090526.1.txt
>
>
> The configuration we have now is pretty complicated. Besides everything else, 
> the mechanism of not specifying parameters separately for maps and reduces 
> leads to problems like HADOOP-5811. This JIRA should address simplifying 
> things and at the same time solving these problems.

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

Reply via email to