[ 
https://issues.apache.org/jira/browse/WHIRR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Kiss updated WHIRR-168:
-----------------------------

    Description: 
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.

  was:
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 I made a patch which adds the possibility to set this 
'whirr.local-socks-proxy-address' to something like
whirr.local-socks-proxy-address=localhost:6666
Instead of configuring the port, we are able to configure the address which 
contains the port.
(also for the sourcecode, it looks much better to not have such a hardcoded 
value.)

In order to run multiple clusters you only need to override this paramter 
knowing that the default value is localhost:6666

        Summary: Extend client side configurations and support core-site.xml, 
mapred-site.xml and hdfs-site.xml instead of hadoop-site.xml  (was: Add a new 
optional c parameter for being able to configure the port of socks connection.)

> 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: local-socks-proxy-address.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

        

Reply via email to