RocketChat / RocketChat/Rocket.Chat
Rocket Chat with MongoDB cluster
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Community Edition.
OS Rocky 8.6
5.0.12 MongoDB / WiredTiber (oplog Enabled).
Rocket Chat 5.1.2
HaProxy 2.4
In daily operation - no issues.
When MongoDB cluster nodes update and restart one-by one in 1h increments RocketChat start to have issues.
-
In Info page "You are operating multiple instances.. some features will not behave as designed." message ?
-
Sending message to "other-users" marks them "gray" as if they were sent, but end user does not receive them.
I don't have picture as I had to solve this ASAP.
The remedy is restart RocketChat service and everything starts working (message 1) is still there thou).
Is this something we do incorrectly?
Or what other information is required?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported rolling MongoDB cluster restart scenario, Rocket.Chat's Info page warning, and message delivery behavior through HAProxy. Reproduce the issue during one-by-one node restarts and trace why messages stop reaching users. Done means the failure cause and required configuration or recovery steps are identified and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100