Missing st2.conf setting for MongoDB connection retries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Close to st2.conf settings for RabbitMQ connection retrites/limits don't work #4775,
there is no way to set maximum number of connection retries for MongoDB in st2.conf.
In K8s environment this is needed to fail on error and rely on K8s algorithms and granular-deployment configuration per each st2 service to re-start and re-schedule Pods.
Because we don't have liveness/readiness probes yet for st2 https://github.com/StackStorm/st2/issues/4020, there is no way to know if service is really in a working state or it's just looping in connection retries and loosing the incoming requests.
We'll need a way to configure MongoDB conneciton retries to be able set no-retry for K8s env in st2.conf.
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 missing setting is identified in conf/st2.conf.sample around lines 107-137; start there and compare the related RabbitMQ retry/limit issue #4775. Trace how MongoDB connection options are configured, with completion meaning st2.conf can set zero or a maximum number of retries for Kubernetes deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, mongodb, python
- Domain
- database, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100