cloudfoundry / cloudfoundry/stratos
Helm: HA Scaling: Ensure database migrations are only run on instance 0
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Now that db migrations are run at startup, we should make sure they only run once.
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
Start by locating the Helm configuration and startup path that run database migrations. Determine how HA instances identify instance 0, then verify that migrations run only there and not on other instances. Done means the deployment behavior is confirmed with relevant startup or deployment checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100