Query timeout on forked target table in standby deployed via fork from primary
Open
Nobody has claimed this yet.
dima
type: bug
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
- Server Version: 5.7.25 OceanBase 4.3.5.3 seekdb (r1.2.0.0) (Built 1-37c93382e5a0d3943dead9...)
Description
When a standby database is deployed via a fork operation from the primary, queries on the target table that was obtained through the fork operation experience timeouts on the standby instance.
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
No source files, tests, reproduction steps, or entry points are identified in the issue. Start by reproducing a query against the forked target table on a standby deployed from the primary, then compare its behavior with the primary and a non-forked standby. Done means the target-table query completes without timing out on the forked standby.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100