Mailing-List: contact dev-help@whirr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@whirr.apache.org
Date: Wed, 2 Nov 2011 16:19:32 +0000 (UTC)
From: "Andrei Savu (Commented) (JIRA)" <jira@apache.org>
To: dev@whirr.apache.org
Message-ID: 
 <1664389405.50892.1320250772322.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <652558307.28345.1319759972400.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (WHIRR-414) whirr can have a non-zero return
 code and unterminated (orphaned) host instances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrei Savu commented on WHIRR-414:
-----------------------------------

Is this approach good enough for now? Do we want something more advanced?
                
> whirr can have a non-zero return code and unterminated (orphaned) host instances
> --------------------------------------------------------------------------------
>
>                 Key: WHIRR-414
>                 URL: https://issues.apache.org/jira/browse/WHIRR-414
>             Project: Whirr
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.6.0
>         Environment: EC2, commandline whirr
>            Reporter: Paul Baclace
>            Assignee: Andrei Savu
>            Priority: Critical
>             Fix For: 0.7.0
>
>         Attachments: WHIRR-414.patch
>
>
> Whirr can fail to completely start a cluster and indicates this with a non-zero return code. In many (currently intermittent) partial failure scenarios, there are resources still active (EC2 machine instances, in my experience) that are not cleaned up. 
> The log contains "IOException: Too many instance failed while bootstrapping!" when I have seen orphaned nodes.
> A non-zero return code should guarantee that all resources are cleaned up.  Without this post-condition, these failures require manual inspection and cleanup to stop useless expenses (which is why I marked this bug critical; it needs to be addressed for any kind of cron job triggered whirr).

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