You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "David Rosenstrauch (JIRA)" <ji...@apache.org> on 2012/09/11 22:38:08 UTC
[jira] [Commented] (WHIRR-168) Extend client side configurations
and support core-site.xml, mapred-site.xml and hdfs-site.xml instead of
hadoop-site.xml
[ https://issues.apache.org/jira/browse/WHIRR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453388#comment-13453388 ]
David Rosenstrauch commented on WHIRR-168:
------------------------------------------
It looks like this enhancement hasn't been released yet. Is there any way to make whirr set properties in the generated client-side hadoop-site.xml file?
> Extend client side configurations and support core-site.xml, mapred-site.xml and hdfs-site.xml instead of hadoop-site.xml
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: WHIRR-168
> URL: https://issues.apache.org/jira/browse/WHIRR-168
> Project: Whirr
> Issue Type: New Feature
> Components: core, service/hadoop
> Environment: ec2
> Reporter: Tibor Kiss
> Assignee: Tibor Kiss
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: core-site.xml, hdfs-site.xml, integration-server-logs.tar.gz, local-socks-proxy-address.patch, mapred-site.xml, whirr-168-1.patch, whirr-168-2.patch, whirr-168-3.patch
>
>
> We have a generated .whirr/<hadoop-cluster-name>/hadoop-proxy.sh which contains a hard coded port value, the 6666.
> In order to be able to start multiple clusters from the same console I needed a simple mechanism to be able to parametrize this port number.
> Therefore is required to extend client side configurations, in the same way as WHIRR-55, to be configurable a 'whirr.hadoop-client.hadoop.socks.server' to something like
> whirr.hadoop-client.hadoop.socks.server=localhost:6667
> The default port will remain of course the 6666.
--
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