GoogleCloudPlatform / GoogleCloudPlatform/click-to-deploy
[k8s][cassandra] race condition during restore process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 465
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 8
Description
Category:
Kubernetes apps
Type:
- Bug
- Feature Request
- Process
There is a race condition during the restore.sh script where the cassandra-restore container is created but is not ready by the time the instance_restore.sh is copied to the cassandra-restore container. The following error is generated: error: unable to upgrade connection: container not found ("cassandra-restore")
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 reading restore.sh and instance_restore.sh, focusing on when the cassandra-restore container is created and when the script is copied into it. Reproduce the restore flow if possible and verify that the copy no longer produces the “container not found” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, kubernetes, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100