ClusterLabs / ClusterLabs/resource-agents
Redis: slave may silently become unconnected to master
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
master_link_status is checked only on demote.
If slave loses it's connection to master there is no way to know about it in pacemaker.
Would be nice to have node attribute reflecting slave connection status so one could decide to write pacemaker rule to collocate resource with slave that is connected to master.
Contributor guide
No contributing guide indexed for this repository
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 inspecting the Redis resource agent and the existing master_link_status check, then trace how Pacemaker node attributes are exposed. Define how loss and recovery of the master connection should be represented; done means a Pacemaker rule can reliably select a slave that remains connected to its master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, shell
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100