<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Andrew Lau <<a href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a>> kirjoitti 1.12.2013 kello 4.55:</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">
p.s. can anyone also confirm, does gluster support multi pathing by default? If I'm using this keepalived method, am I bottle necking myself to one host?</div></div></blockquote><br></div><div>If you are using native GlusterFS, either FUSE or libgfapi, then client only fetches volume information from server with floating IP. Client connects directly to servers defined in volume specification. If you are running Gluster daemon on every oVirt node, then you could also use localhost:/glusterVol to mount your GlusterFS volume. Of course this is not good way to go if you ever plan to add a node without Gluster daemon.</div><div><br></div><div>So, the answer is: you are not bottlenecking to one host if you are using native GlusterFS. With NFS it's connecting to one host only.</div><div><br></div><div>-samuli</div><br></body></html>