[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: MTU on tun0

First I have cluster of 5 servers. Those are physical machines.

I've installed it many times through ansible and now I see that one machine has different config
which tells different MTU in node-config.yaml (1400 - others having 1450)

Maybe I was wrong with ansible - I thought that it is ansible problem when - because when I've
installed my cluster every time it went linke in your situation. Some nodes having MTU set to
1500 and some to 1450. origin-node services was started same as origin-master service.

You are BTW right - now I've checked that after reboot MTU is set to 1500 on my first node
even if MTU is set to 1450 in its node-config. 

This is probably an issue inside openshift logic - it is not reading or properly setting the MTU
after server reboot. 

I've solved this by simply setting MTU to 1450 on each node manually because I am not in
production mode.

This should be reported to Open Shift crew.

David Strejc
t: +420734270131

On Fri, Feb 12, 2016 at 10:02 AM, Per Carlson <pelle hemmop com> wrote:
Hi David.

On 12 February 2016 at 09:45, David Strejc <david strejc gmail com> wrote:
This is a ansible installer problem.

I had similar issue with my instalation and this is really important. Without MTU set to 1450 there is
a problem with traffic between nodes. I've spent four hours debugging our MySQL galera cluster on Nodes
which didn't want to synchronize but servers saw each other. It was due to MTU problem.

​How could this be an ansible problem? The tun0-interface is created on the fly when starting the node. And ansible did the job setting up the correct MTU in the node-config.yaml files.

Could you give some pointers how you resolved your issue?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]