somejfn commented on issue #2890: KVMHAMonitor thread blocks indefinitely while 
NFS not available
URL: https://github.com/apache/cloudstack/issues/2890#issuecomment-433896656
 
 
   Correct.  Only VM-HA enabled would get restarted and create a duplicate
   when the host goes down.  Still,  I don't think this a good behavior to
   fire VM-HA (because of host Up --> Down state) under any scenarios caused
   by transient storage disconnection.   If  the host goes down after 5
   minutes,  VM-HA restarts VM about one minute later, and then if the NFS
   issue gets resolved you have almost 100% probability of root disk
   corruption and you don't know where the 2 VMs are since Cloudstack only
   remembers the last copy it started.
   
   
   On Mon, Oct 29, 2018 at 3:21 AM Boris Stoyanov - a.k.a Bobby <
   notificati...@github.com> wrote:
   
   > hi @csquire <https://github.com/csquire> @somejfn
   > <https://github.com/somejfn>, thanks for this issue!
   >
   > I think it's correct that the host goes into 'Down' state after loosing
   > it's grip on the storage, since this is basically making it inoperable.
   > Going into 'Disconnected' state would only mean the connection between
   > management and host is compromised.
   >
   > On the other hand duplicated VMs is definitely something that needs to get
   > addressed, prior marking the host as 'Down' when we have a VM-HA enabled.
   > Just to be sure, can you please confirm you don't see these duplicated VMs
   > on a non VM-ha enabled instances? I'd like to narrow down this issue and
   > make sure it's in the VM-HA logic.
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/cloudstack/issues/2890#issuecomment-433810696>,
   > or mute the thread
   > 
<https://github.com/notifications/unsubscribe-auth/AOflqLPAw0oQ2_po-4BHKpzHRDZMUc9Hks5upqxxgaJpZM4XNOD8>
   > .
   >
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to