pingcap / pingcap/tidb

[crrf]restore fail for without replication-status-sub-prefix param

Open
#69,110 2 comments 0 reactions 1 assignee Claimed by @RidRisR View on GitHub
component/br may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/critical type/bug
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)

1. enable CRRF

2. restore to downstream

3. check restore status

### 2. What did you expect to see? (Required)
restore success
### 3. What did you see instead (Required)
restore fail
[2026/06/10 02:25:32.019 +00:00] [ERROR] [main.go:43] ["br failed"] [error="retain-latest-mvcc-version requires compact-log-backup compactions with cal-shift-ts enabled, minimal-compaction-size=0, complete TS coverage over [466696674146516993, 466876663332864000], and complete shards: [BR:Common:ErrInvalidArgument]invalid argument"] [errorVerbose="[BR:Common:ErrInvalidArgument]invalid argument\nretain-latest-mvcc-version requires compact-log-backup compactions with cal-shift-ts enabled, minimal-compaction-size=0, complete TS coverage over [466696674146516993, 466876663332864000], and complete shards

Image
Image

replication-status-sub-prefix is not set during restore

### 4. What is your TiDB version? (Required)

v8.5.6-tidb-advancer-10578-dev

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.