RocketChat / RocketChat/Rocket.Chat

Notifications doesn't work with multipie instances in 6.4.2

Open
#30,694 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

We decided to update RC from 5.x to lasted 6.4.2 version, and after update we saw that notifications doesn't work anymore - sound and desktop, with browser or electron client.
Also we don't see at admin panel IP-address of any instance and it's hearbeat:

image

Does 6.4.2 supports such setup or it is some bug? it's like described here - https://docs.rocket.chat/deploy/deploy-rocket.chat/scaling-rocket.chat/running-multiple-instances only difference - we're using docker images. And 3.x, 4.x and 5.x worked smoothly with this setup.

Server Setup Information:
  • Version of Rocket.Chat Server: 6.4.2
  • Operating System: containers with debian 11
  • Deployment Method: docker
  • Number of Running Instances: 20
  • NodeJS Version: v14.21.3
  • MongoDB Version: 5.0.21 / wiredTiger (oplog Enabled)

We tested update to 6.4.2 on test installation with only one app instance - and notifications work pretty well on it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked multiple-instances deployment documentation and reproduce the reported Docker setup, comparing one instance with 20 instances on Rocket.Chat 6.4.2. Investigate why browser and Electron notifications stop working and why the admin panel lacks instance IP addresses and heartbeat data; done means both behaviors work in the multi-instance deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, electron
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.