-
Notifications
You must be signed in to change notification settings - Fork 283
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
ticdc lag is more than 4m after inject one tikv network partition to all #8809
Comments
/remove-area dm |
/unassign @overvenus |
/severity major |
By the design |
@nongfushanquan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@nongfushanquan what is the root cause? |
Does this issue can be fixed by #8858 ? |
/close |
@nongfushanquan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What did you do?
1、run tpcc with threads 10 and warehouse 1000
2、After 10 minutes, simulates one of tikv is network isolated from other all pods
fault start time:2023-04-18 10:44:27
3、After 10 minutes, recovery the fault
fault recover time:2023-04-18 10:54:27
What did you expect to see?
changefeed lag is less than 30s
What did you see instead?
ticdc lag is more than 4m after inject fault
Versions of the cluster
git hash:5252420517ce5497ed053aa6322fdb2a33f898e1
The text was updated successfully, but these errors were encountered: