br: log the replica # in backup and restore
Open
component/br
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
In order to analyze failure due to replica number difference, we need to record the replica number and other topology related information in br log.
Contributor guide
Research direction
Start by locating the BR backup and restore logging entry points in the TiDB repository and trace where replica and topology information is available. Done means BR logs include the replica number and other topology-related information needed to analyze replica-number differences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100