<p dir="ltr">Hi Mathew,</p>
<p dir="ltr">If you use FUSE mount, the client is connecting to all servers in the volume and thus it works like MPIO.<br>
For example - 3 replica volume has the same data in all 3 gluster servers and thus the cluent has 3 'paths' to the volume.<br>
If one fails, a timeout will occur and thr client will stop trying to update that server's bricks.</p>
<p dir="ltr">Of course, you can have multiple IPs defined per gluster server and thus the client will try to reach the server's bricks by any IP in the configuration.</p>
<p dir="ltr">For example, Brick A has '<a href="http://192.168.1.2">192.168.1.2</a>' & '<a href="http://192.168.2.2">192.168.2.2</a>'. There will be no constant connection over both IPs, but as far as I know the client will try the second IP.</p>
<p dir="ltr">Best Regards,<br>
Strahil Nikolov</p>
<div class="quote">On Aug 23, 2019 20:35, Matthew Evans <runmatt@live.com> wrote:<br type='attribution'><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:'calibri' , 'helvetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Does Gluster support any sort of MPIO-like functionality for a single client? Maybe when using a Distributed Stripe? Or is a single client always limited to the throughput of a single node for each session?<br />
</div>
</div>
</blockquote></div>