Standby fails to switch back to primary with ERROR 4012 (HY000): Timeout despite consistent log positions

Open
#301 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
databases, distributed-systems

Research direction

The issue names no source files, tests, or entry points. Start by reproducing the standby-to-primary switch on seekdb 4.3.5.3 and inspect the timeout path for ERROR 4012; done means the role switch succeeds when log positions are consistent.

Written by the indexing model from the issue text.

Description

dima

Environment

  • Server version: OceanBase 4.3.5.3 seekdb (r1.2.0.0)
  • Build: 1-e536cfa77c25c6fde5e541fcdee9ead835a41d43 Mar 13 2026
  • Hardware: cpu 8 memeo...

Description

When attempting to switch a standby database back to the primary role, the operation fails with the error ERROR 4012 (HY000): Timeout. This occurs even though there is no data heterogeneity and the log positions between the primary and standby are confirmed to be consistent.

Impact

The standby database cannot be promoted to primary, affecting high availability and failover capabilities.

Additional Context

This issue is specific to the seekdb version of OceanBase.

Creator: cms-cms

Dominant language
C++
Stars
2.9k
Forks
342
Avg merge
2d 14h
Merged PRs (30d)
53

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oceanbase/seekdb

All issues in oceanbase/seekdb

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.