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

Support change the make up replica behavior online #1727

Open
disksing opened this issue Sep 3, 2019 · 15 comments
Open

Support change the make up replica behavior online #1727

disksing opened this issue Sep 3, 2019 · 15 comments
Assignees
Labels
difficulty/easy Easy task. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. type/enhancement The issue or PR belongs to an enhancement.

Comments

@disksing
Copy link
Contributor

disksing commented Sep 3, 2019

PCP Issue

  • difficult: Easy
  • score: 100
  • min score required: 0
  • Recommended Skills: Go

Description

The default behavior we handle offline/down peer is to create an operator to replace it. It is safe but could be very slow. Sometimes the user may want to delete it directly (for example, disk broken, data is gone for sure), we can add a configuration to help.

@disksing disksing added the type/enhancement The issue or PR belongs to an enhancement. label Sep 3, 2019
@rleungx
Copy link
Member

rleungx commented Oct 10, 2019

I think we need to provide a way to delete the peers directly on a specified store which can not be recovered.

@disksing
Copy link
Contributor Author

@rleungx I think that is a better idea!

@nolouch nolouch changed the title Support change the make up replica behavior online PCP: Support change the make up replica behavior online Oct 22, 2019
@nolouch nolouch added PCP difficulty/easy Easy task. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed PCP labels Oct 22, 2019
@miyuri-fox
Copy link

/pick-up-challenge

@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

@miyuri-fox pick up issue success

@sourcelliu
Copy link
Contributor

/pick-up-challenge

@sre-bot
Copy link
Contributor

sre-bot commented Dec 23, 2019

@mantuliu pick up issue success

@sourcelliu
Copy link
Contributor

/give-up-challenge

@sre-bot
Copy link
Contributor

sre-bot commented Jan 6, 2020

@mantuliu give up issue success

@you06 you06 changed the title PCP: Support change the make up replica behavior online Support change the make up replica behavior online Feb 29, 2020
@gzgywh
Copy link

gzgywh commented Mar 3, 2020

/pick-up-challenge

@sre-bot
Copy link
Contributor

sre-bot commented Mar 3, 2020

@gzgywh pick up issue success

@you06
Copy link
Contributor

you06 commented Mar 30, 2020

@gzgywh Dear contributor, our rules has been updated. We will remove your pick if there is no update in 7 days(but feel free to pick up again).

@sre-bot
Copy link
Contributor

sre-bot commented Apr 6, 2020

This pick has been automatically canceled after more than a week.

@JmPotato
Copy link
Member

@disksing @rleungx Do we have a way in PD to automatically judge whether a store is in specified states (for example, disk broken, data is gone for sure) which can not be recovered now? If the answer is yes, maybe we can just do some work in scheduler to do so. If it's not, providing a way like API or command line tool may be a good idea.

@disksing
Copy link
Contributor Author

disksing commented Aug 3, 2020

@JmPotato I think there is no such mechanism. I have a second thought here. It seems a global configuration to control the behaviour could work too, especially if it introduces a lot complexity to add APIs to manipulate some store states.

@JmPotato
Copy link
Member

JmPotato commented Aug 3, 2020

@disksing I have the same feeling that maybe introducing a configuration used to control the scheduler's behaviour in this situation is better. In more detail, with this configuration enabled, scheduler will not try to replace the offline/down peer, but just delete it directly. And the making up work will be done by the replica checker.

@JmPotato JmPotato self-assigned this Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/easy Easy task. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

No branches or pull requests

9 participants