[
https://issues.apache.org/jira/browse/WHIRR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052353#comment-13052353
]
Tom White commented on WHIRR-332:
---------------------------------
This would be a useful improvement. I don't think it is dependent on WHIRR-318,
but the property naming should be designed in the context of that JIRA.
E.g. should it be whirr.templates.roles.${role}.hardware-id, or perhaps even
_roles_: whirr.templates.roles.hadoop-namenode+hadoop-jobtracker.hardware-id.
> Need to specify different instance size/type depending on role
> --------------------------------------------------------------
>
> Key: WHIRR-332
> URL: https://issues.apache.org/jira/browse/WHIRR-332
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.5.0
> Reporter: Paul Baclace
>
> When setting up Hadoop, whirr.hardware-id is used in the configuration to set
> a single instance size/type for both nn,jt and dn,tt roles, but there are
> workloads that benefit from having a different instance size/type for each
> role. This need is even greater for ensembles with Zookeeper and HBase.
> Without this, a small Whirr cluster underutilizes resources.
> whirr.hardware-id should be a used to set a default instance size/type, and
> variations like whirr.${role}.hardware-id could be used to set size/type more
> specifically. This is a simple, obvious, and easy to implement mechanism to
> provide this functionality.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
