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.

Sign up for GitHub

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

Jump to bottom

A notification mechanism is required when TiKV is restarted after 35 minutes of downtime #1863

Closed
benmaoer opened this issue Mar 4, 2020 · 3 comments
Closed

A notification mechanism is required when TiKV is restarted after 35 minutes of downtime #1863

benmaoer opened this issue Mar 4, 2020 · 3 comments
Labels
area/controller enhancement New feature or request status/help-wanted Extra attention is needed

Comments

@benmaoer
Copy link

benmaoer commented Mar 4, 2020 •
edited
Loading

Feature Request

A notification mechanism is required when TiKV is restarted after 35 minutes of downtime. Now, the cluster has more TiKV instances than we needs.
Furthermore, the data of the crashed TiKV instance has lagged behind other instances. At this time, the evict-leader scheduling strategy needs to be added for the crash TiKV to avoid significant increase in response delay.
@weekface weekface added area/controller enhancement New feature or request labels Mar 4, 2020
@DanielZhangQD
Copy link
Contributor

@benmaoer Thanks for reporting this issue, we will evaluate this request.

@cofyc cofyc added the status/help-wanted Extra attention is needed label Jun 8, 2020
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days

@DanielZhangQD
Copy link
Contributor

More events are added in #2150.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/controller enhancement New feature or request status/help-wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@weekface @cofyc @benmaoer @DanielZhangQD