[
https://issues.apache.org/jira/browse/OOZIE-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236668#comment-13236668
]
[email protected] commented on OOZIE-779:
-----------------------------------------------------
bq. On 2012-03-23 01:14:02, Mohammad Islam wrote:
bq. > +1.
bq. > The question is: how it is working now without this extra settings.
it my case I was always testing with YARN in same host and local port, that it
is why i didn't see it. I you had Hadoop site.xml injected in your Oozie setup,
the value was picked up from there.
Our QA folks found this out testing in a cluster.
- Alejandro
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4455/#review6262
-----------------------------------------------------------
On 2012-03-22 21:27:55, Alejandro Abdelnur wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4455/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-03-22 21:27:55)
bq.
bq.
bq. Review request for oozie.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. A bug in Hadoop MAPREDUCE-4044 prevents the JobClient to process correctly
'mapred.job.tracker'.
bq.
bq. To avoid this, until Hadoop fixes it, we should inject the jobtracker
host:port using the 3 possible properties for it:
bq.
bq. * mapred.job.tracker
bq. * mapreduce.jobtracker.address
bq. * yarn.resourcemanager.address
bq.
bq.
bq. This addresses bug OOZIE-779.
bq. https://issues.apache.org/jira/browse/OOZIE-779
bq.
bq.
bq. Diffs
bq. -----
bq.
bq.
trunk/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
1304075
bq.
bq. Diff: https://reviews.apache.org/r/4455/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. built/deployed and submitted jobs to a hadoop 0.23 cluster running in a
non-default port
bq.
bq.
bq. Thanks,
bq.
bq. Alejandro
bq.
bq.
> Oozie cannot submit jobs to hadoop 0.23 if running in non-default host:port
> ---------------------------------------------------------------------------
>
> Key: OOZIE-779
> URL: https://issues.apache.org/jira/browse/OOZIE-779
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 3.2.0
>
>
> A bug in Hadoop MAPREDUCE-4044 prevents the JobClient to process correctly
> 'mapred.job.tracker'.
> To avoid this, until Hadoop fixes it, we should inject the jobtracker
> host:port using the 3 possible properties for it:
> * mapred.job.tracker
> * mapreduce.jobtracker.address
> * yarn.resourcemanager.address
--
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
