I'm a RabbitMQ core team member (have been for close to 7 years and contributor for about 10 years), so I have some idea about how things work internally.
There are no leader and follower nodes in Erlang. All nodes are equal as far as Erlang is concerned (we will ignore C and hidden nodes for
the sake of this discussion since RabbitMQ cluster members are neither).
[1] explains what is replicated in a RabbitMQ cluster. There are no special nodes in RabbitMQ. Again, all nodes are equal.
What is not equal is queue replicas. They do have a leader and 0 or more followers. Classic mirrored queues use a homegrown
leader election algorithm while quorum queues [3] rely on Raft's leader election part.
[2] explains that any client can connect to any node. That should give you some idea that indeed, in most ways nodes are not
special.
[4], which I happened to be a contributor to, clearly explains that by default a queue resides on a single node. Technically there is a master
replica but there are no followers, so again, all nodes are semantically identical for any practical purpose unless replication comes into play.
When a cluster is formed [5] or restarted [6], nodes temporarily become "special" because at least one has to serve as a seed or recovery
point. Again, by most definitions and given the transient nature of this "designation" this node is not a "leader", just the very first node to have
started.
HTTP API and management plugin used to have a dedicated cluster node. That's no longer the case as of 3.6.7 [7], every node collects
and serves its own metrics unless it has to aggregate. When it does reach out to peers for their data to aggregate, there are no leaders
or followers.
I also should point out that your arrogant attitude is not appreciated on this list. If you are so incredibly smart and know better then why are you on this list asking
questions? Just go ahead and read the source. Continue behaving like this and you will end up banned in no time.