[WHIRR-168] Extend client side configurations and support core-site.xml, mapred-site.xml and hdfs-site.xml instead of hadoop-site.xml

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 0.9.0
• Component/s: core, service/hadoop

Environment

ec2

• Assignee: Tibor Kiss
• Reporter: Tibor Kiss
• Created: 20/Dec/10 17:50
• Updated: 11/Sep/12 20:37

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.

Issue Links

• blocks: WHIRR-301 Improve code testability
• is related to: WHIRR-294 Separate Hadoop install and configuration scripts into more generic functions
• relates to: WHIRR-224 Allow control over adding AWS credentials to local hadoop-site.xml for S3