br: restore pod oom protection during tikv grpc request retry
Open
affects-9.0
component/br
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
BR restore process has introduced oom and ood protection to tikv nodes in recent release (9.0 and above), where tikv will deny the backup file downloading requests. At that time, br restore pod will issue instant retry.
Currently, the retry is issued immediately and the accumulated requests could occupy a lot memory and cause oom at br pod.
BR restore need to throttle the retry to avoid the request flood.
Contributor guide
Assessment
This issue has not been assessed yet.