Mesh based on EoIP. I get 100%CPU and 100% load on EoIP

Hi all.
I have some issue with mesh. What I am doing exactly: I want to make roaming for office wifi users. I have 5 APs mikrotik 952U 5ac2ND , in future it will be 9APs.
I connect APs each to each - there 4 connection on AP - via EoIP. I use 172.16.255.0/24 network
Then I creating mesh interface and adding port, port is a EoIP

But on some stages of adding ports to mesh interface I get 100%load on EoIP and 100%CPU load.
EoIP name like ap1-ap6 and so on.
Picture from Winbox
I’m deactivate mesh port “ap1-ap8” and after 10-20 secs - all going to normalized. load on CPU and EoIP goes down
Picture from Winbox

What it can be and who to resolve this?

Sounds like a loop.
Routing loops are possible, if a mesh network is attached to a RSTP network in two or more points!

I’m also thinking about loop, but I don’t know how to prevent this?
And I’m think I don’t understood what you say

I’d like to ask why did you decide to go with a mesh in the first place. I’d go and connect all APs to each other with a cable, if at all possible.

A common misbelief exists that wireless mesh somehow assists in roaming- in fact it does not!

Now all APs, except two APs - this APs use 5Ghz connection to others, connected via cable. I found this document where used EoIP and APs connected via cable to create roaming, so I try to repeat. May bee I should try to do “roaming” based on access list and signal strenght ?

And I tried discover when my mesh will go crazy and after what it calm down:
In this case all fine
Picture from Winbox
Schema what port is active

When I activated mesh port from ap6-ap9 on AP6 and port ap9-ap6 on AP9 - cpu and eoip load 100%
To make this I deactivated port ap6-ap9 on AP6 and port ap9-ap6 on AP9 and ap6-ap8 on AP6
Mkrotik goes crazy. there are 4 routers on the picture
Schema what port was activate and than remove

I try my best - if need other information or you do not understand written, please write here what exactly and I and I will try to rewrite.

You don’t need to do anything special. WiFi roaming is a function of client, not AP. I recommend reading a couple of great posts on the topic: first, second.

And I do not recommend kicking off clients based on signal strength to force them roam- this usually makes roaming experience worse.

From my experience, the best roaming results can be achieved when using CAPsMAN with local forwarding turned off.