As per the error message, there has been some kind of communication error between the different nodes in the cluster; which has caused the specified node to take over as the orchestrator node in the cluster.
Sounds like some kind of operator-initiated server shutdown.