Dedicated instance of a Sitecore CM publication in a load-balanced environment

Question

We need to set up a load-balanced CM environment for Sitecore - mainly for fault-tolerant tasks, but also at times when the load can become too heavy. For this, we will have two servers. I looked at the scaling guide and they mention that in a load-balanced CM environment, you need to have one server dedicated to publishing. The note says that this is mainly for performance, but I heard people claim that if you do not configure a dedicated publication instance, the publication queues are not synchronized. I guess I understand this based on how the sitecore publishing queue works, but what is the point of having a balanced CM CM environment if there is a dependency on one of the servers? The provided is not a dependence on the site, but its dependence, nevertheless, is there any way around this?

Edit

I have a few answers here that indicate that it could be a performance issue or a deadlock issue, so I think my real question is how to make the switch to another resource for a dedicated publication instance, as now an exceptional copy of the publication will become the central point of failure.

Answer 1

- . CM , , , , . , , , 2 CM, .

, , . . 3- CM-: 2 CM 1 , . ( Sitecore 7.2) , , . , , 10 , , , -.

, .

, , , - , , , , , "" CM , t20 > . , (.disabled), / , , . , , , , . , , , .

Answer 2

, CM, . , , , , . HTTP- CMS, , . , , , , , , , .

, CM, . , , .

Answer 3

Sitecore " ", 27

CM , , . CM , . CM . ,

Thus, mainly for performance, deployment, and other considerations, this is also not the "Load Balance" setting, as sitecore calls it the Multi-Instance setting, which means that the authors will enter each instance separately and not allow the load balance to be determined by the server. which CM instance to use.