ClusterLabs / ClusterLabs/resource-agents
Question: best way to send a signal to all clone instances
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
Not sure if this is the right place to ask this question...
I have created a resource agent tailored for my service. Now I have several clones of this service that loads its configuration from a shared filesystem. This service can also reload its configuration while running when it receives SIGUSR1. Easy task on a single node, but I'm wondering what is the best way to do it with Pacemaker clones so that every instance receives the signal. There is no need to send the signal precisely at the same time, but the shorter the interval between first and last signal the better. Any ideas?
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start by reviewing Pacemaker clone behavior and the resource-agent interface for coordinating actions across instances. Done would require a documented, agreed mechanism for signaling every clone with a bounded interval between signals.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100