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

(dr-autosync) v6.5.8 scale in one node from primary datacenter failed during async mode #16465

Closed
mayjiang0203 opened this issue Jan 30, 2024 · 2 comments · Fixed by #16467 or #16486
Closed

Comments

@mayjiang0203
Copy link

Bug Report

What version of TiKV are you using?

v6.5.8

What operating system and CPU are you using?

Steps to reproduce

  1. deploy one tidb cluster with 12 stores, and config it with 5 replicas in dr-auto-sync mode.
  2. down two tikvs in the backup center, make replication mode switch to async.
  3. Try to scale-in one node in the primary center.

What did you expect?

Scale in succeeded.

What did happened?

Scale in hung.

Didn't hit it before #16174.

@mayjiang0203 mayjiang0203 added the type/bug Type: Issue - Confirmed a bug label Jan 30, 2024
@mayjiang0203
Copy link
Author

/severity major

@tonyxuqqi
Copy link
Contributor

In this case, does the back-up site have two learners for each region?
If that's the case, it would be blocked by today's check as we likely run into 3 healthy peers and 3 unhealthy peers. And if the remove peer happens on the healthy peer, it would be blocked.
The argument here is that if the unhealthy peer is learner, then it should not be counted. Then we will have only 3 healthy peers plus one unhealthy learner. By demoting a healthy peer, we will still have 2 healthy voter which can achieve majority.

ti-chi-bot bot pushed a commit that referenced this issue Jan 31, 2024
close #16465

improve the remove peer check. Only check when the updating role is voter

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Jan 31, 2024
close tikv#16465

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Jan 31, 2024
close tikv#16465

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this issue Jan 31, 2024
close #16465

improve the remove peer check. Only check when the updating role is voter

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>

Co-authored-by: tonyxuqqi <tonyxuqi@outlook.com>
tonyxuqqi added a commit to ti-chi-bot/tikv that referenced this issue Jan 31, 2024
close tikv#16465

improve the remove peer check. Only check when the updating role is voter

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
tonyxuqqi added a commit to ti-chi-bot/tikv that referenced this issue Jan 31, 2024
close tikv#16465

improve the remove peer check. Only check when the updating role is voter

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
ti-chi-bot bot pushed a commit that referenced this issue Feb 1, 2024
ref #16465

Improve readability

Signed-off-by: Yang Zhang <yang.zhang@pingcap.com>
ti-chi-bot bot pushed a commit that referenced this issue Feb 1, 2024
close #16465

revert the remove peer check. Without this revert, the scale-in will be blocked when there're one slow or down peer in a region of the scale-in node.

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
RidRisR pushed a commit to RidRisR/tikv that referenced this issue Feb 2, 2024
ref tikv#16465

Improve readability

Signed-off-by: Yang Zhang <yang.zhang@pingcap.com>
Signed-off-by: RidRisR <79858083+RidRisR@users.noreply.github.com>
ti-chi-bot bot pushed a commit that referenced this issue Feb 2, 2024
)

close #16465

When calculating the impact of conf change, include all operations into considerations.

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
tonyxuqqi added a commit to ti-chi-bot/tikv that referenced this issue Feb 2, 2024
…v#16486)

close tikv#16465

When calculating the impact of conf change, include all operations into considerations.

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
ti-chi-bot pushed a commit to ti-chi-bot/tikv that referenced this issue Feb 2, 2024
close tikv#16465

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this issue Feb 6, 2024
) (#16489)

close #16465

When calculating the impact of conf change, include all operations into considerations.

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>

Co-authored-by: tonyxuqqi <tonyxuqi@outlook.com>
dbsid pushed a commit to dbsid/tikv that referenced this issue Mar 24, 2024
close tikv#16465

improve the remove peer check. Only check when the updating role is voter

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
Signed-off-by: dbsid <chenhuansheng@pingcap.com>
dbsid pushed a commit to dbsid/tikv that referenced this issue Mar 24, 2024
ref tikv#16465

Improve readability

Signed-off-by: Yang Zhang <yang.zhang@pingcap.com>
Signed-off-by: dbsid <chenhuansheng@pingcap.com>
dbsid pushed a commit to dbsid/tikv that referenced this issue Mar 24, 2024
…v#16486)

close tikv#16465

When calculating the impact of conf change, include all operations into considerations.

Signed-off-by: tonyxuqqi <tonyxuqi@outlook.com>
Signed-off-by: dbsid <chenhuansheng@pingcap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants