[
https://issues.apache.org/jira/browse/OOZIE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246510#comment-13246510
]
[email protected] commented on OOZIE-802:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4636/#review6688
-----------------------------------------------------------
Ship it!
+1
- Mayank
On 2012-04-04 14:14:36, Alejandro Abdelnur wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4636/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-04-04 14:14:36)
bq.
bq.
bq. Review request for oozie.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. in MR2 (Hadoop 0.23) the configuration used by a client to submit jobs to
the cluster is used to configure the AM.
bq.
bq. Currently this configuration is whatever has been set in hadoop-conf/
which is minimal (setting yarn framework).
bq.
bq. A problem arises in how AM and HS communicate to each other info a about a
job (via HDFS), AM using default conf values writes to /tmp while HS started by
minicluster looks in target/test-dir thus producing random failures. Random
because if the AM is still alive when the client checks for the job, the AM
gives the info correctly, but if the AM is gone the HS does not know about the
job.
bq.
bq. We should seed the configuration of minicluster as the hadoop-conf/ used
by the testcases.
bq.
bq.
bq. This addresses bug OOZIE-802.
bq. https://issues.apache.org/jira/browse/OOZIE-802
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. trunk/core/src/test/java/org/apache/oozie/test/XTestCase.java 1309391
bq.
bq. Diff: https://reviews.apache.org/r/4636/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. run testcases with hadoop 1 and Hadoop 0.23
bq.
bq.
bq. Thanks,
bq.
bq. Alejandro
bq.
bq.
> Add minicluster config as hadoop-site.xml for testcases
> --------------------------------------------------------
>
> Key: OOZIE-802
> URL: https://issues.apache.org/jira/browse/OOZIE-802
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 3.2.0
>
>
> in MR2 (Hadoop 0.23) the configuration used by a client to submit jobs to the
> cluster is used to configure the AM.
> Currently this configuration is whatever has been set in hadoop-conf/ which
> is minimal (setting yarn framework).
> A problem arises in how AM and HS communicate to each other info a about a
> job (via HDFS), AM using default conf values writes to /tmp while HS started
> by minicluster looks in target/test-dir thus producing random failures.
> Random because if the AM is still alive when the client checks for the job,
> the AM gives the info correctly, but if the AM is gone the HS does not know
> about the job.
> We should seed the configuration of minicluster as the hadoop-conf/ used by
> the testcases.
--
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
