[Gluster-users] MTU size issue?

[Sander Zijlstra]

LS,

I recently reconfigured one of my gluster nodes and forgot to update the MTU size on the switch while I did configure the host with jumbo frames.

The result was that the complete cluster had communication issues.

All systems are part of a distributed striped volume with a replica size of 2 but still the cluster was completely unusable until I updated the switch port to accept jumbo frames rather than to discard them.

The symptoms were:

- Gluster clients had a very hard time reading the volume information and thus couldn’t do any filesystem ops on them.
- The glusterfs servers could see each other (peer status) and a volume info command was ok, but a volume status command would not return or would return a “staging failed” error.

I know MTU size mixing and don’t fragment bit’s can screw up a lot but why wasn’t that gluster peer just discarded from the cluster so that not all clients kept on communicating with it and causing all sorts of errors.

I use glusterFS 3.6.2 at the moment…..

Kind regards
Sander



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151014/9db8d0bd/attachment.sig>