yujun777 opened a new pull request, #30303: URL: https://github.com/apache/doris/pull/30303
Sometimes we want to drop specific replicas on the given backend. We may use sql cmd 'admin set replica status = bad' to set the replica bad, and drop it later. But it has two bad things: 1. If the replica num is 1 or 2, set one replica bad will make both read and write failed; 2. Even replica num is 3, set bad command is not always working. If the tablet is big, clone a new tablet may take long. During that time, if the replica writing new data and increase replica version, then if be report tablet is good, then fe will auto change this replica from bad to ok (because version is increase and be report it ok). So we add cmd to set replica status as drop. It's very like set replica as bad. But it solve the two bad things above. When set a replica as drop, this replica is still both readable and writable. After clone a new health tablet on another backend, this replica can safely drop then. ## Proposed changes Issue Number: close #xxx <!--Describe your changes.--> ## Further comments If this is a relatively large or complex change, kick off the discussion at [d...@doris.apache.org](mailto:d...@doris.apache.org) by explaining why you chose the solution you did and what alternatives you considered, etc... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
