[
https://issues.apache.org/jira/browse/BIGTOP-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042304#comment-14042304
]
Evans Ye commented on BIGTOP-1310:
----------------------------------
Okay, thanks for providing the new build #270. Just as [~rvs] said, hbase build
doesn't up to date. Right now the [jenkins
repo|http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Repository/label=centos6/270/artifact/repo/]
can not provision a well running hadoop cluster due to the protobuf version
between hadoop(2.5.0) and hbase(2.4.0a) are not compatible. In order to sort
this out I think fixing those jenkins builds will be something we need to deal
with first.
Shall we prioritize current existing builds in to groups? Maybe put trunk
builds into first priority group and we aim on fixing them as our first stage
to clean up our CI. After that we then decide a bunch of builds into second
priority group and so on. Just like [~jayunit100] said that we probably will
not going to fix those low priority or long failing builds. In such a case we
just wiped them out. Would this be a possible solution?
> 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)
