Standby fails to pull from primary and hangs during initialization in multi-tablet scenario
Open
Nobody has claimed this yet.
dima
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
- Version: seekdb (OceanBase seekdb 1.2.0.0)
- Revision: 1-e536cfa77c25c6fde5e541fcdee9ead835a41d43
- Build Branch: feat_rootservice_lite
- Build Time: Mar 13 2026 10:54:44
- Build Flags: RelWithDebInfo|Sanity
Description
In a primary-standby deployment with multiple tablets, the standby cluster fails to pull data from the primary cluster. The process hangs indefinitely during its initialization phase.
Impact
The standby cluster cannot be established, preventing high availability and disaster recovery capabilities.
Priority
High (blocks standby setup)
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 reproducing a multi-tablet primary-standby setup with the reported seekdb version and trace the standby initialization and primary data-pull path. The work is done when the standby completes initialization and successfully pulls data from the primary without hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100