[
https://issues.apache.org/jira/browse/WHIRR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995990#comment-12995990
]
Tom White commented on WHIRR-168:
---------------------------------
That looks like the problem - do you want to test it works?
Thinking about this more, should we support configuration by users in standard
Hadoop XML config files? Doing so would avoid problems with quoting that users
might not be aware of. This could be in addition to the way we currently (so
I'm not proposing we don't commit this patch). Thoughts?
> 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
> Attachments: core-site.xml, hdfs-site.xml,
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
