You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Sean Zhang (Commented) (JIRA)" <ji...@apache.org> on 2012/03/22 20:14:22 UTC

[jira] [Commented] (WHIRR-63) Support EC2 Cluster Compute Groups for Hadoop

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

Sean Zhang commented on WHIRR-63:
---------------------------------

As Adrian suggested 
"
if you choose templateBuilder.fastest() using the aws-ec2 provider, a cluster compute instance will be used and setup placement group automatically.

if you want to specify placementgroup manually use AWSEC2TemplateOptions.placementGroup
"

'fastest' function could be a nice thing to expose, but it is not the solution to this problem. I think we have to go with calling placementGroup explicitly, but placementGroup is not exposed in the TemplateOptions interface. Any suggestions?

                
> Support EC2 Cluster Compute Groups for Hadoop
> ---------------------------------------------
>
>                 Key: WHIRR-63
>                 URL: https://issues.apache.org/jira/browse/WHIRR-63
>             Project: Whirr
>          Issue Type: New Feature
>          Components: service/hadoop
>            Reporter: Tom White
>             Fix For: 0.9.0
>
>
> We should support the new EC2 cluster compute groups which have high bandwidth between nodes in the cluster. See http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?using_cluster_computing.html

--
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