Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: abhinandanprateek <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1640-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1640-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1640: CLOUDSTACK-9458: Fix HA bug when VMs are stopped on ...
Content-Type: text/plain
Message-Id: <20161122050512.5EBD8E0999@git1-us-west.apache.org>
Date: Tue, 22 Nov 2016 05:05:12 +0000 (UTC)
archived-at: Tue, 22 Nov 2016 05:05:15 -0000

Github user abhinandanprateek commented on the issue:

    https://github.com/apache/cloudstack/pull/1640
  
    @marcaurele for a host that is found to be down we go ahead and schedule a restart for HA enabled VM, this is good.
    
    For the VMs that are not HA enabled they will continue to show as running.  This works in the scenario where the host finally comes around. What if host is gone for long or forever, then the VMs will continue to show as running. The user will have to guess that he has to stop and then start the VM.  Can you check if VMs will be eventually marked down by VM sync ? If that is the case, I think this fix should be good then 
    
    Another suggestion: In the specific case where host drops and then come back in certain interval. Can we make the parameter that times out to mark a host down as configurable. In your case you can increase it to several hours and it will not start HA during that time and host can still connect back ?
    

---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---