[
https://issues.apache.org/jira/browse/WHIRR-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497503#comment-13497503
]
Steve Loughran commented on WHIRR-682:
--------------------------------------
# Deploying a cluster with template: {{whirr.instance-templates=1
hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker,
hadoop-datanode+hadoop-tasktracker}} failed; the endpoint sent messages back
saying the caller was over a limit (and suggesting a retry time).
# This was not picked up as a retry event -it was converted into an error and
considered a cluster instantiation failure.
# the VMs did get created, but were not saved to the cluster instances file -as
that was not created.
The underlying problem is the failure to wait for further operations (though
it's interesting that Nova did create the VMs); the failure to notice the VMs
up is a followup issue
> OpenStack Nova throttling prevents Whirr from bringing up clusters with
> multiple nodes
> --------------------------------------------------------------------------------------
>
> Key: WHIRR-682
> URL: https://issues.apache.org/jira/browse/WHIRR-682
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.9.0
> Environment: whirr.provider=rackspace-cloudservers-uk
> Reporter: Steve Loughran
>
> You can't create a 3 node hadoop cluster on OpenStack Nova, because it
> rate-limits VM requests (in time and per-day). The endpoints send a 413-coded
> message, but this is not detected as a retryable action
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
