You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/07/22 05:02:39 UTC
[jira] [Commented] (BIGTOP-1310) Vagrant recipes provision 2.0
hadoop w/ puppet recipes that are compatible with 2.2
[ https://issues.apache.org/jira/browse/BIGTOP-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069744#comment-14069744 ]
jay vyas commented on BIGTOP-1310:
----------------------------------
Okay, update on this:
*original issue of bad shuffle parameter in yarn-site.xml*: the final step in this JIRA (changing the mapreduce.aux_services.shuffle parameter, and then restarting yarn services) is a sufficient workaround to hold us over to bigtop 0.8.0 release. https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+BigTop+0.7.0+hadoop+on+CentOS+with+puppet.
*next steps:* we will CLOSE this jira by UPDATING the recipes to point to SNAPSHOT when BIGTOP-1323 is done and then jenkins build is fixed. agreed ?
> 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)