I have a weird issue while trying to connect to a remote Mongo replica set. This is my setup: on a remote machine I have three instances of MongoDB running on different ports, each belonging to the same replocal replica…
When I deploy a simple flask application on AKS with one replica, the application is running as expected. But when I deploy the application with two replicas, it was not working as expected. User not able to redirect home page…
Let’s say I have 5 nodes replica set. 3 of them are dead, 2 alive. How would the majority will be calculated? 5 nodes majority would be 5/2+1=3 but if 3 nodes are dead, will it still look for 3…
Do anybody manage to start existed relicaset after MongoDB minor version upgrade from official MongoDB stable repo? On previous versions 5.0.14/4.4.18 everything works perfect. {"t":{"$date":"2023-02-24T12:22:59.994+01:00"},"s":"I", "c":"-", "id":4333218, "ctx":"LogicalSessionCacheReap","msg":"Rescheduling the next replica set monitoring request","attr":{"replicaSet":"MainRepSet","host":"10.1.0.4:27017","delayMillis":0}} {"t":{"$date":"2023-02-24T12:22:59.996+01:00"},"s":"I", "c":"REPL", "id":21783, "ctx":"BackgroundSync","msg":"Waiting for pings…
I am using three nodes for my MongoDB replica set, one as the primary node, one as a secondary node, and one as an arbitrator node. I am using the following connection string in Golang to connect with MongoDB. opts…
I am attempting to run a MongoDB cluster locally to test transactions. I've leveraged the Bitnami docker-compose file version: '2' services: mongodb-primary: image: 'bitnami/mongodb:latest' environment: - MONGODB_ADVERTISED_HOSTNAME=mongodb-primary - MONGODB_REPLICA_SET_MODE=primary - MONGODB_ROOT_PASSWORD=password123 - MONGODB_REPLICA_SET_KEY=replicasetkey123 ports: - 27017:27017 volumes: - 'mongodb_master_data:/bitnami' mongodb-secondary:…
Is it possible to "ask" Kubernetes Deployment to create ReplicaSet with custom name? E.g. I want it to be nginx-replicaset1 instead of nginx-8576854954
I'm using a replicaset with 3 nodes. Node primary with name n1 and port 27018, secondaries n2 port 27019 and n3 por 27020. I would like to switch to any secondady node from primary. I've tried with mongo -host n2…
I'm using Oracle Virtualbox to host 3 VM running CentOS 7. Vbox network setup is: primary-db Adapter1: NAT Mode, no forwarding rules in network settings & Adapter2: Bridge Mode, promiscuous mode=Allow all secondary-db1 Adapter1: NAT Mode, no forwarding rules in…