[
https://issues.apache.org/jira/browse/BIGTOP-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628705#comment-13628705
]
Konstantin Boudnik commented on BIGTOP-919:
-------------------------------------------
Actually, if you look into cluster.pp you'll see something like
{noformat}
hadoop::datanode { "datanode":
namenode_host => $hadoop_namenode_host,
namenode_port => $hadoop_namenode_port,
dirs => $hdfs_data_dirs,
auth => $hadoop_security_authentication,
ha => $hadoop_ha,
}
{noformat}
which should explain where the {{ha}} comes from. Doesn't look like a valid
ticket to me.
> wrong variable "ha" in puppet hadoop templates (core-site.xml, hdfs-site.xml)
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-919
> URL: https://issues.apache.org/jira/browse/BIGTOP-919
> Project: Bigtop
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 0.6.0
> Environment: N/A
> Reporter: Prakash Sidaraddi
> Priority: Critical
> Labels: deploy,deployment, puppet
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> variable name hadoop_ha changed in cluster.pp but not reflected in templates
> core-site.xml and hdfs-site.xml because of which puppet deployment throws
> error.
> variable name "ha" in all the templates (wherever referred) has to be changed
> to "hadoop_ha"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
