Open liushuang00o opened 5 years ago
We see this in 0.74.3, also. If a mongo replica set member goes down, Rocket Chat quits working. Seems like this defeats the purpose of a redundant mongo replica set.
Confirmed on version 1.0.3 The same problem.
in 1.1.1 same problem
1.2.1 still there
2.4.2 still there
3 and beyond still an issue. This is a huge issue...can we get some attention to it?
Still an issue on 4.5.0.
Hi,
Description:
We are running a multi-instances of Rocket.Chat. Use Mongodb Replica Set
Extract of one Docker Compose file :
But Mongodb Replica Set doesn’t work properly.
Steps to reproduce:
1)shutdown the master mongodb 192.168.3.70
2)Check the rs.status()
Now we can see 192.168.3.71 is PRIMARY,it's right.
3)View the log display as follows.
192.168.3.70:27017 closed, but 192.168.3.71:27017 timed out.
4)Telnet 192.168.3.71 27017
Server Setup Information:
Version of Rocket.Chat Version: 0.73.2 Operating System: Centos 7.5 Deployment Method: Docker Number of Running Instances: 2 DB Replicaset Oplog: enabled NodeJS Version: 8.11.3 - x64 MongoDB Version: 4.0.5
Thanks,
Dou