[
https://issues.apache.org/jira/browse/BIGTOP-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041332#comment-14041332
]
Roman Shaposhnik commented on BIGTOP-1310:
------------------------------------------
[~jayunit100] [~evans_ye] in general our nightly builds are 100% deployable
from these repos:
http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Repository/
in the usual apt/yum/zypper way. The repos/list files are located under each
platform's lastSuccessfulBuild. For example, here's where the repo file for
CentOS6 is:
http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Repository/label=centos6/lastSuccessfulBuild/artifact/repo/
That's the theory. The practice, however, is that our build system was wedged
for quite some time now and some of the components haven't been updated in
those nightly repos. Hadoop, for example, is ok, but HBase is not. It would be
really nice if we can get to a full green build ASAP. Your help would be more
than welcome.
> Vagrant recipes provision 2.0 hadoop w/ puppet recipes that are compatible
> with 2.2
> -----------------------------------------------------------------------------------
>
> Key: BIGTOP-1310
> URL: https://issues.apache.org/jira/browse/BIGTOP-1310
> Project: Bigtop
> Issue Type: Bug
> Reporter: jay vyas
>
> I'm noticing in the Vagrant recipe, that if i do
> {noformat}
> vagrant up bigtop1
> {noformat}
> I get an error :
> bq. "Invalid shuffle port number -1"
> I then have to change the do
> {noformat}
> <value>mapreduce.shuffle</value>
> {noformat}
> And it works !
> I looked further and saw that BIGTOP-1118 actually changed the value , for
> hadoop 2.2.
> So this means hadoop 2.0 is NOT compatible with bigtop puppet recipes, which
> are built for hadoop 2.2+ anymore.
> 1) We need to gaurd puppet recipes: They should only be applied to the
> appropriate hadoop version. Is there a way to do this?
> 2) We need to upgrade vagrant incantations to provison current bigtop if
> theres a way to do that, or at least hard code them to 2.2 , rather than 2.0.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
