-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Jepsen monotonic test failed with anomalies #48802
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.0
affects-6.1
affects-6.2
affects-6.3
affects-6.4
affects-6.5
affects-6.6
affects-7.0
affects-7.1
affects-7.2
affects-7.3
affects-7.4
affects-7.5
severity/critical
sig/transaction
SIG:Transaction
type/bug
This issue is a bug.
Comments
Close this and create a detailed issue in the tikv repo tikv/tikv#16069. |
ti-chi-bot bot
added a commit
to tikv/tikv
that referenced
this issue
Nov 27, 2023
close #16069, close pingcap/tidb#48802 When a peer is removed, it is necessary to update its apply state because this peer may be simultaneously taking a snapshot. An outdated apply state will invalidate the coprocessor cache assumption and potentially lead to a violation of linearizability (returning stale cache). Signed-off-by: Neil Shen <overvenus@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Nov 27, 2023
close tikv#16069, close pingcap/tidb#48802 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
This was referenced Nov 27, 2023
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Nov 27, 2023
close tikv#16069, close pingcap/tidb#48802 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
Nov 27, 2023
close tikv#16069, close pingcap/tidb#48802 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot
pushed a commit
to tikv/tikv
that referenced
this issue
Nov 27, 2023
close #16069, close pingcap/tidb#48802 When a peer is removed, it is necessary to update its apply state because this peer may be simultaneously taking a snapshot. An outdated apply state will invalidate the coprocessor cache assumption and potentially lead to a violation of linearizability (returning stale cache). Signed-off-by: Neil Shen <overvenus@gmail.com> Co-authored-by: Neil Shen <overvenus@gmail.com>
overvenus
added a commit
to ti-chi-bot/tikv
that referenced
this issue
Nov 27, 2023
close tikv#16069, close pingcap/tidb#48802 When a peer is removed, it is necessary to update its apply state because this peer may be simultaneously taking a snapshot. An outdated apply state will invalidate the coprocessor cache assumption and potentially lead to a violation of linearizability (returning stale cache). Signed-off-by: Neil Shen <overvenus@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com> Signed-off-by: Neil Shen <overvenus@gmail.com>
ti-chi-bot bot
pushed a commit
to tikv/tikv
that referenced
this issue
Nov 27, 2023
close #16069, close pingcap/tidb#48802 When a peer is removed, it is necessary to update its apply state because this peer may be simultaneously taking a snapshot. An outdated apply state will invalidate the coprocessor cache assumption and potentially lead to a violation of linearizability (returning stale cache). Signed-off-by: Neil Shen <overvenus@gmail.com> Co-authored-by: Neil Shen <overvenus@gmail.com>
ti-chi-bot bot
added a commit
to tikv/tikv
that referenced
this issue
Nov 29, 2023
close #16069, close pingcap/tidb#48802 When a peer is removed, it is necessary to update its apply state because this peer may be simultaneously taking a snapshot. An outdated apply state will invalidate the coprocessor cache assumption and potentially lead to a violation of linearizability (returning stale cache). Signed-off-by: Neil Shen <overvenus@gmail.com> Co-authored-by: Neil Shen <overvenus@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.0
affects-6.1
affects-6.2
affects-6.3
affects-6.4
affects-6.5
affects-6.6
affects-7.0
affects-7.1
affects-7.2
affects-7.3
affects-7.4
affects-7.5
severity/critical
sig/transaction
SIG:Transaction
type/bug
This issue is a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
run jepsen test
2. What did you expect to see? (Required)
no error reported
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
master & release-7.5
The text was updated successfully, but these errors were encountered: