You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bitnami Chart will run this script on first Pod (not primary one)
So this script should handle that and try to connect to the primary one
failed to add role clusterMonitor to user "rocketchat"; Error: rs0 [direct: secondary] admin>
MongoServerError: not primary> ... ... ... ... ... ... ... ... Uncaught
rs0 [direct: secondary] admin>
rs0 [direct: secondary] admin>
this script will work correctly on initial install, not later upgrades/restarts
I think a better approach would be moving this script to a simple job and waiting for primary before running script (or making a replica set connection to primary node in current approach)
as you can see it's connecting in a direct way witch is incorrect
Problem solved After setting
mongodb:
initdbScriptsConfigMap: ""
Before setting this we will get restart loops on first mongodb instance after upgrades/restarts when first instance is not primary
The text was updated successfully, but these errors were encountered:
Bitnami Chart will run this script on first Pod (not primary one)
So this script should handle that and try to connect to the primary one
this script will work correctly on initial install, not later upgrades/restarts
I think a better approach would be moving this script to a simple job and waiting for primary before running script (or making a replica set connection to primary node in current approach)
as you can see it's connecting in a direct way witch is incorrect
Problem solved After setting
Before setting this we will get restart loops on first mongodb instance after upgrades/restarts when first instance is not primary
The text was updated successfully, but these errors were encountered: