BeaconCMS / BeaconCMS/beacon_live_admin
Fails to call functions in the cluster after reconnects
Open
bug
roadmap
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
After a net split it will fail to call functions in previous defined nodes, eg:
```
** (Beacon.LiveAdmin.ClusterError) failed to call Beacon.Authorization.get_agent(...)
Got:
no running node found for site :dockyard_com
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Beacon.LiveAdmin.ClusterError message and the failed Beacon.Authorization.get_agent call, then trace how cluster nodes are selected after a network split and reconnect. Reproduce the reconnect scenario and verify that functions on previously defined nodes can be called again without the no-running-node error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100