Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce the impact of network isolation recovery #2538

Open
nolouch opened this issue Jun 15, 2020 · 0 comments
Open

Reduce the impact of network isolation recovery #2538

nolouch opened this issue Jun 15, 2020 · 0 comments
Labels
component/schedule Scheduling logic. epic/co-attributes relative data attributes. status/TODO The issue will be done in the future. type/enhancement The issue or PR belongs to an enhancement.

Comments

@nolouch
Copy link
Contributor

nolouch commented Jun 15, 2020

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

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
@nolouch nolouch added type/enhancement The issue or PR belongs to an enhancement. component/schedule Scheduling logic. epic/co-attributes relative data attributes. labels Jun 15, 2020
@rleungx rleungx added the status/TODO The issue will be done in the future. label Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/schedule Scheduling logic. epic/co-attributes relative data attributes. status/TODO The issue will be done in the future. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

No branches or pull requests

2 participants