[ 
https://issues.apache.org/jira/browse/BIGTOP-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017951#comment-14017951
 ] 

Evans Ye commented on BIGTOP-1310:
----------------------------------

I also agree that vagrant provisioner should stick together with current bigtop 
version. However I don't know much about the repository currently we use:
{code}
http://bigtop.s3.amazonaws.com/releases/0.7.0/redhat/6/x86_64
{code}
I just grep it from the repo file in [bigtop installation 
guide|https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+Hadoop+distribution+from+Bigtop+0.6.0].

To fix this, as long as we can always build and upload the newest rpm up to the 
S3 repository, it should be easy. We can just hard code the snapshot 
repository. 
Another way is to fulfill the compatibility between 2.0 and 2.2 by puppet 
recipes.
We can write a puppet facter to auto detect hadoop version and use simple 
if-else in yarn-site.xml template to determine which value we should place.
Last one , just like [~jayunit100] said, may be we can just hard code them to 
2.2, and I can run through a test on puppet recipes against the new hadoop 
version.


> 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)

Reply via email to