You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tibor Kiss (JIRA)" <ji...@apache.org> on 2011/02/13 00:35:57 UTC

[jira] Issue Comment Edited: (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=12994001#comment-12994001 ] 

Tibor Kiss edited comment on WHIRR-168 at 2/12/11 11:35 PM:
------------------------------------------------------------

I extended HadoopConfigurationBuilder to support 'hadoop-client' prefix too.
In HadoopNameNodeClusterActionHandler#createClientSideProperties then I made the changes to support core-site.xml, mapred-site.xml and hdfs-site.xml instead of the deprecated hadoop-site.xml.

In the HadoopProxy#getProxyCommand I am using the cluster.getConfiguration().getProperty("hadoop.socks.server") instead of the hardcoded one.

Tom, could you review the patch? Especially the configuration compositions in HadoopNameNodeClusterActionHandler#createClientSideProperties.

      was (Author: tibor.kiss):
    I extended HadoopConfigurationBuilder to support 'hadoop-client' prefix too.
In HadoopNameNodeClusterActionHandler#createClientSideProperties then I made the changes to support core-site.xml, mapred-site.xml and hdfs-site.xml instead of the deprecated hadoop-site.xml.

In the HadoopProxy#getProxyCommand I am using the cluster.getConfiguration().getProperty("hadoop.socks.server") instead of the hardcoded one.
  
> 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, whirr-168-1.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