You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2018/12/06 08:47:52 UTC

[GitHub] Overv opened a new issue #3082: Why do nodes restart when an NFS mount fails?

Overv opened a new issue #3082: Why do nodes restart when an NFS mount fails?
URL: https://github.com/apache/cloudstack/issues/3082
 
 
   It seems that the CloudStack agent forces a restart of a node when one of the primary storage NFS mounts fails, even if there are no VMs currently using a volume on it. That means that it takes just one NFS hickup to take down an entire cluster. Why was this design decision made and will it be changed at some point?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services