Issues at adding an arbiter in a PSA configuration

Ops and Admin Replication
#1

Hi, guys. I’m using MongoDB 5.0.5 hosted on RHEL7 servers. I tried to deploy a PSA configuration, but I was only succeeded in the PS part: adding the arbiter has been very difficult. When I thought I got it, after the addArb command, rs.status() output shows me the following message, and I will show you the most important part of it:
{
…
stateStr: ‘(not reachable/healthy)’,
…
lastHeartbeatMessage: ‘Error connecting to hl_arbiters.dops.etecsa.cu:27056 (172.16.1.179:27056) :: caused by :: Permission denied’,
…
}

Also, I got this meesage from the arbiter Mongod instance’s log, even before I run the addArb command:

“ctx”:“monitoring-keys-for-HMAC”,“msg”:“Failed to refresh key cache”,“attr”:{“error”:“NotYetInitialized: Cannot use non-local read concern until replica set is finished initializing.”,“nextWakeupMillis”:7600}}

I tried almost everything, from configure the firewall in RHEL7 servers to customize SELinux, because I used an unusual port for the arbiter (I want to deploy two arbiters, really, that’s the reason why I didn’t use 27017). Nothing changed, I still cannot deploy my PSA architecture. What am I doing wrong? Thanks in advance.

#2

Why do you want to add two arbiters.You should have only one arbiter
From mongo docs

WARNING
** In general, avoid deploying more than one arbiter per replica set.**

May be nodes are unable to communicate on port 27056
Did you try with 27017 with single arbiter?
Also how was arbiter started like bindIp params etc
Do you see waiting for connections in the log?

1 Like