processone / processone/ejabberd
Message is not routed to all session in different nodes.
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 6.7k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I am running a cluster of 2 nodes, which having these following sessions in sm table
| username | node | resource | priority |
|---|---|---|---|
| alice | ejabberd@node1.com | alice_001 | 0 |
| alice | ejabberd@node2.com | alice_002 | 0 |
| bob | ejabberd@node2.com | bob_001 | 0 |
When bob send message to alice only alice session which is in the same node as bob (node2) can receive the message.
ejabberd-21.01.7- Ejabberd clustering is up properly means either node is down the service still continue to work.
NOTE :
It is working again after i restart both nodes.. and it is stop working after a while so i need to restart the both nodes time after time.. plz help..
I don't use cache for sm
sm_use_cache: false
Please help to advice.
Thanks.
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 reproducing the issue with the two-node cluster and the sessions shown in the sm table, keeping sm_use_cache: false. Investigate why messages from bob reach only the local alice session after the cluster has been running for a while. Done means messages consistently reach all of Alice's sessions across both nodes without restarting them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100