oceanbase / oceanbase/obdeploy
[Question]: OBD server DR handling (Reopen)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 95
- Forks
- 136
- PR merge metrics
- No merged PRs in 30d
Description
Description
I want to reopen case.
https://github.com/oceanbase/obdeploy/issues/218
The reply focus on OCP, I didn't have any objection about that.
But it is not a reason not to handle OBD's HA/DR function.
If the only OBD server is down, we lose the control for cluster.
Using a worst case, my only OBD server down and my cluster down incidentally. I still can try using second OBD server to start the cluster again if it is existed.
Using other product for sample, like kubernetes cluster, we need three control plane to sure that we still can control pod even one control plane down.
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 issue #218 and this reopening request to understand the earlier OCP discussion and the requested OBD HA/DR behavior. Define the scope for retaining cluster control when one OBD server is unavailable, including whether another OBD server should support recovery. Done should be a decided, implementable requirement rather than an unresolved design question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100