[
https://issues.apache.org/jira/browse/MESOS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264189#comment-13264189
]
[email protected] commented on MESOS-182:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4922/
-----------------------------------------------------------
(Updated 2012-04-28 01:27:41.349376)
Review request for mesos, Charles Reiss and Matei Zaharia.
Changes
-------
Added Charles as a reviewer since he had reviewed this stuff for me before.
Summary
-------
I wanted to break down the changes to Hadoop so that someone could see exactly
how minimal they really are. In addition, I wanted the patches to the Hadoop
source code itself to be clearly identifiable. So, I broke the mega patch up.
Now, we apply the small Hadoop patch (which has been submitted to Hadoop
trunk), COPY the Mesos contrib code over, and then apply two other small
patches for hadoop-env.sh and mapred-site.xml.
In addition, we also copy the native library into lib as well as the mesos.jar
and protobuf.jar so that we don't need to point to any build directory.
Likewise, we don't even need to set MESOS_NATIVE_LIBRARY at all! The resulting
patch for hadoop-env.sh is very small indeed.
I also deleted the hadoop.tar.gz that we included because I figured it would be
just as easy to download it via the tutorial (once it's downloaded once, the
tutorial just keeps using that, only deleting it if you do a 'make clean').
The final directory you get after running 'make hadoop-0.20.205.0' can be
zipped, copied, and used right away in a Mesos cluster.
I also used the patch from https://issues.apache.org/jira/browse/MESOS-182 to
do the same thing for cdh3u3. You get this via 'make hadoop-0.20.2-cdh3u3'.
This addresses bug MESOS-182.
https://issues.apache.org/jira/browse/MESOS-182
Diffs
-----
Makefile.am 99a21d7
README 0d58255
configure.ac f1e2c3a
ec2/Makefile.am PRE-CREATION
hadoop/Makefile.am PRE-CREATION
hadoop/TUTORIAL 36f5fb0
hadoop/TUTORIAL.sh c122387
hadoop/hadoop-0.20.2-cdh3u3.patch PRE-CREATION
hadoop/hadoop-0.20.2-cdh3u3_hadoop-env.sh.patch PRE-CREATION
hadoop/hadoop-0.20.2-cdh3u3_mesos.patch PRE-CREATION
hadoop/hadoop-0.20.205.0.patch c113001
hadoop/hadoop-0.20.205.0.tar.gz bc605a3
hadoop/hadoop-0.20.205.0_conf_hadoop-env.sh.patch 6733ef5
hadoop/hadoop-0.20.205.0_conf_mapred-site.xml.patch 4764496
hadoop/hadoop-0.20.205.0_hadoop-env.sh.patch PRE-CREATION
hadoop/hadoop-0.20.205.0_mesos.patch PRE-CREATION
hadoop/mapred-site.xml.patch PRE-CREATION
hadoop/mesos-executor PRE-CREATION
hadoop/mesos/build.xml PRE-CREATION
hadoop/mesos/ivy.xml PRE-CREATION
hadoop/mesos/ivy/libraries.properties PRE-CREATION
hadoop/mesos/src/java/org/apache/hadoop/mapred/FrameworkExecutor.java
PRE-CREATION
hadoop/mesos/src/java/org/apache/hadoop/mapred/FrameworkScheduler.java
PRE-CREATION
hadoop/mesos/src/java/org/apache/hadoop/mapred/HadoopFrameworkMessage.java
PRE-CREATION
hadoop/mesos/src/java/org/apache/hadoop/mapred/MesosScheduler.java
PRE-CREATION
hadoop/mesos/src/java/org/apache/hadoop/mapred/MesosTaskTrackerInstrumentation.java
PRE-CREATION
Diff: https://reviews.apache.org/r/4922/diff
Testing
-------
$ pwd
/path/to/mesos/build
$ make hadoop-0.20.205.0
$ make hadoop-0.20.2-cdh3u3
Thanks,
Benjamin
> Patch for CDH3u3 for mesos 0.9.0
> --------------------------------
>
> Key: MESOS-182
> URL: https://issues.apache.org/jira/browse/MESOS-182
> Project: Mesos
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.9.0
> Reporter: Hiral Patel
> Priority: Trivial
> Labels: patch
> Attachments:
> 0001-Manually-patched-using-0.20.250-patch-for-mesos-plus.patch
>
>
> I've attached a patch for cdh3u3 which uses the patch for 0.20.205 as a bases
> plus adds protobuff jar and a mesos-0.9.0.jar compiled from RC3. I tested it
> on my local machine with wordcount to validate the tasks run on mesos.
--
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
