Search before asking
Description
Each row binlog tablet must be located on the same backend and storage path as its corresponding base tablet. However, replica repair, relocation, or balancing may schedule them independently and break this locality, causing insufficient valid replica pairs and load failures.
The scheduler should preserve base/binlog tablet locality during replica creation, repair, relocation, and deletion.
Use case
For tables with row binlog enabled, backend failures, disk failures, balancing, and decommissioning should not break the base/binlog tablet pairing. After scheduling, every row binlog replica should remain on the same backend and storage path as its base replica, ensuring that writes and binlog reads remain available.
Related issues
#65265
#65804
#62058
Are you willing to submit PR?
Code of Conduct
Search before asking
Description
Each row binlog tablet must be located on the same backend and storage path as its corresponding base tablet. However, replica repair, relocation, or balancing may schedule them independently and break this locality, causing insufficient valid replica pairs and load failures.
The scheduler should preserve base/binlog tablet locality during replica creation, repair, relocation, and deletion.
Use case
For tables with row binlog enabled, backend failures, disk failures, balancing, and decommissioning should not break the base/binlog tablet pairing. After scheduling, every row binlog replica should remain on the same backend and storage path as its base replica, ensuring that writes and binlog reads remain available.
Related issues
#65265
#65804
#62058
Are you willing to submit PR?
Code of Conduct