You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (Commented) (JIRA)" <ji...@apache.org> on 2011/12/29 07:46:30 UTC

[jira] [Commented] (WHIRR-332) Need to specify different instance size/type depending on role

    [ https://issues.apache.org/jira/browse/WHIRR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177024#comment-13177024 ] 

Tom White commented on WHIRR-332:
---------------------------------

I would remove the deprecated role name aliases in a separate JIRA so that folks scanning release notes see it, since it's an incompatible change.

The test should check that roles that haven't been configured to use a particular type of hardware fall back to the default. Also, in testHardwareIdPerInstanceTemplate, what if only role1 has its hardware configured (i.e. not role1+role2) - it should fail or warn.

Looks good otherwise. 

                
> 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
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-332.patch, WHIRR-332.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira