how to configure cluster backends like redis,zookeeper
Open
Nobody has claimed this yet.
documentation
enhancement
good first issue
help wanted
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Does st2.conf file support adding redundant pairs of backend coordinator like zookeeper or redis?
We have zookeeper cluster (3 instances) but not sure how to include 3 instances in st2.conf.
Tried below config but doesn't work.
[coordination]
url = kazoo://user:pass@host1:2181/,
kazoo://user:pass@host2:2181/,
kazoo://user:pass@host3:2181/
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
The issue points to st2.conf, specifically the [coordination] section and its url setting. Start by tracing how that setting is parsed and how backend endpoints are passed to the coordinator; done means the supported three-node configuration is established or the limitation and correct syntax are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis
- Domain
- devops, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100