[
https://issues.apache.org/jira/browse/MAPREDUCE-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283176#comment-13283176
]
Harsh J commented on MAPREDUCE-2384:
------------------------------------
Since this is trivial: Just adds in a test that compiles fine, passes for now
and can help prevent regressions of this nature in future refactoring of the
submit path (validated by running it against 1.x, where it is indeed broken,
but is not critical in any way), I'm going ahead with the commit by Monday
unless someone has raised an objection.
Thanks,
Harsh
> Can MR make error response Immediately?
> ---------------------------------------
>
> Key: MAPREDUCE-2384
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2384
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: job submission
> Affects Versions: 0.21.0
> Reporter: Denny Ye
> Assignee: Harsh J
> Attachments: MAPREDUCE-2384.r1.diff, MAPREDUCE-2384.r2.diff,
> MAPREDUCE-2384.r3.diff, MAPREDUCE-2384.r4.diff
>
>
> When I read the source code of MapReduce in Hadoop 0.21.0, sometimes it made
> me confused about error response. For example:
> 1. JobSubmitter checking output for each job. MapReduce makes rule to
> limit that each job output must be not exist to avoid fault overwrite. In my
> opinion, MR should verify output at the point of client submitting. Actually,
> it copies related files to specified target and then, doing the verifying.
> 2. JobTracker. Job has been submitted to JobTracker. In first step,
> JT create JIT object that is very "huge" . Next step, JT start to verify job
> queue authority and memory requirements.
>
> In normal case, verifying client input then response immediately if
> any cases in fault. Regular logic can be performed if all the inputs have
> passed.
> It seems like that those code does not make sense for understanding.
> Is only my personal opinion? Wish someone help me to explain the details.
> Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
