You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2013/08/06 04:43:47 UTC
[jira] [Assigned] (BIGTOP-987) Update hadoop-conf-pseudo package
config to be in sync with puppet configs
[ https://issues.apache.org/jira/browse/BIGTOP-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik reassigned BIGTOP-987:
---------------------------------------
Assignee: Henry Wang
Henry, assigning to you and hope you'd have a chance to submit a patch!
> Update hadoop-conf-pseudo package config to be in sync with puppet configs
> --------------------------------------------------------------------------
>
> Key: BIGTOP-987
> URL: https://issues.apache.org/jira/browse/BIGTOP-987
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.6.0
> Reporter: Mark Grover
> Assignee: Henry Wang
> Fix For: 0.7.0
>
>
> During some poking around with the hadoop-conf-pseudo package, I noticed that the configuration was not the same as with a cluster deployed using Bigtop's puppet code. In particular, the staging directory being used in hadoop-conf-pseudo deployed cluster is in /tmp/ on HDFS while it's under user's home directory in puppet code. Seems like those configs have diverged. I would vouch that the puppet configs are the source of truth here, so let's update the hadoop-conf-pseudo configs to match up with those from the puppet code.
--
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