tikv / tikv/pd

Reduce the impact of network isolation recovery

Open
#2,538 0 comments 0 reactions 0 assignees View on GitHub
component/schedule epic/co-attributes status/TODO type/enhancement
Dominant language
Go
Stars
1.2k
Forks
783
Avg merge
5d 21h
Merged PRs (30d)
36

Description

## Feature Request

### Is your feature request related to a problem? Please describe:

We do a network isolation test (about 5h). When recovering, the IO of the quarantined machine has a great impact.
![image](https://user-images.githubusercontent.com/6428910/84646085-23159a80-af34-11ea-93bb-b98b42f04a02.png)

### Describe the feature you'd like:

It should be scheduled when the store's io drops. and do not schedule when the store's io is high.

### Describe alternatives you've considered:

Need to identify abnormal node recovery scenarios
### Teachability, Documentation, Adoption, Migration Strategy:

- Go

Contributor guide

Open the contributing guide

Research direction

No files, tests, or code entry points are named. Start by locating the network isolation recovery flow and how store IO is measured and scheduled; clarify the abnormal node recovery scenarios and define done as recovery work being deferred during high store IO without disrupting normal recovery.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.