Peer Discovery with DNS record wont cluster about rabbitmq-server

[womblep]

I have turned up debugging and I think it is to do with my load balancer health check not bringing the node up (and putting it into DNS) until it can ping the traffic port.
The new check of "is the node's IP address in the DNS list?" is tripping me up.

[womblep]

Yep, AWS Network Load Balancer is expecting some port available to send TCP requests to for the health check before it will put the IP address in the DNS entry. The traffic port is not available until the clustering has happened so I am stuck in a catch-22.

Is there a port which RabbitMQ has open when it starts? I tried 4369 but that doesnt seem to work either.

Otherwise we need a config item to bypass this check:

    ThisNode = node(),
    ThisNodeIsIncluded = lists:member(ThisNode, Nodes),
    case ThisNodeIsIncluded of
        true ->
            ok;
        false ->
            ?LOG_DEBUG(
               "Peer discovery: not satisfyied with discovered peers: the "
               "list does not contain this node",
               #{domain => ?RMQLOG_DOMAIN_PEER_DISC})
    end,

which is a good check but in this instance is not required or desired