won"t there be any problems with mysql"s performance under high concurrency when using master-slave semi-Synchronize replication scheme? After all, semi-Synchronize also has a delay, which will slightly block the thread

in addition, I think there is MHA+Keepalived "s master-slave scheme MHA for failover high availability, but suppose the following scheme: two master, do each other mysql master-slave use keepalived to expose virtual IP, one master backups multiple slave through keepalived external service and the other master backup multiple slave is based on the current service master behind this virtual IP
when a master failure occurs, Another master provides services through keepalived, so it doesn"t have to fail over. Why do you need a MHA?