somejfn commented on issue #2890: KVMHAMonitor thread blocks indefinitely while 
NFS not available
URL: https://github.com/apache/cloudstack/issues/2890#issuecomment-433911908
 
 
   With NFS not available and since those are hard mounts,  even a "virsh
   destroy" would not work.  Libvirtd will block until the NFS mount issue is
   resolved.     I think that ideally the cloudstack-agent would do every task
   in a non-blocking way and not be affected by primary storage hiccups.   For
   instance,  to avoid the thread pool blocking on libvirtd tasks,  why no
   implement a configurable timeout on thosetasks with sensible defaults ?   I
   don't see a good reason a call to libvirtd take more than a few seconds
   (beside known long lasting tasks such as live migration)
   
   As for fencing,  afaik the host HA framework was created for the purpose or
   reliable fencing... but will cause more damage than good if the end result
   is to reboot all KVM hosts via IPMI (compared to just wait for NFS to come
   back)
   
   On Mon, Oct 29, 2018 at 9:18 AM Boris Stoyanov - a.k.a Bobby <
   [email protected]> wrote:
   
   > I think the leanest way to fence the resource would be, prior to setting
   > the host down to iterate all it's VMs and shut them down, only then to
   > proceed and mark the host as 'Down', once were there, there's no issue with
   > VM-HA starting a new instance on a separate host.
   > I guess this needs further investigation and a fix as described.
   >
   > —
   > 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-433906239>,
   > or mute the thread
   > 
<https://github.com/notifications/unsubscribe-auth/AOflqMVZGtW3QGGlL-DfyzMy6duL7EXQks5upwAhgaJpZM4XNOD8>
   > .
   >
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to