There seems to be a pretty severe bug with using hosted engine on gluster.

If the host that was used as the initial hosted-engine --deploy host goes away, 
the engine VM wil crash and cannot be restarted until the host comes back.

This is regardless of which host the engine was currently running.

The issue seems to be buried in the bowels of VDSM and is not an issue with 
gluster itself.

The gluster filesystem is still accessable from the host that was running the 
engine. The issue has been submitted to bugzilla but the fix is some way off 

Can my hosted engine be converted to use NFS (using the gluster NFS server on 
the same filesystem) without rebuilding my hosted engine (ie change 
domainType=glusterfs to domainType=nfs)?

What effect would that have on the hosted-engine storage domain inside oVirt, 
ie would the same filesystem be mounted twice or would it just break.

Will this actually fix the problem, does it have the same issue when the hosted 
engine is on NFS?



The contents of this electronic message and any attachments are intended only 
for the addressee and may contain legally privileged, personal, sensitive or 
confidential information. If you are not the intended addressee, and have 
received this email, any transmission, distribution, downloading, printing or 
photocopying of the contents of this message or attachments is strictly 
prohibited. Any legal privilege or confidentiality attached to this message and 
attachments is not waived, lost or destroyed by reason of delivery to any 
person other than intended addressee. If you have received this message and are 
not the intended addressee you should notify the sender by return email and 
destroy all copies of the message and any attachments. Unless expressly 
attributed, the views expressed in this email do not necessarily represent the 
views of the company.
Users mailing list

Reply via email to