-
Notifications
You must be signed in to change notification settings - Fork 287
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
ScanRegions total retry time is too short #5230
Labels
affects-4.0
affects-5.0
affects-5.1
affects-5.2
affects-5.3
affects-5.4
affects-6.0
affects-6.1
area/ticdc
Issues or PRs related to TiCDC.
component/kv-client
TiKV kv log client component.
report/customer
Customers have encountered this bug.
severity/moderate
type/bug
The issue is confirmed as a bug.
Comments
overvenus
added
type/bug
The issue is confirmed as a bug.
component/kv-client
TiKV kv log client component.
area/ticdc
Issues or PRs related to TiCDC.
affects-5.3
affects-5.2
affects-5.1
affects-5.0
affects-4.0
affects-5.4
affects-6.0
labels
Apr 21, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Apr 30, 2022
This was referenced Apr 30, 2022
Find a new case reproduce the issue. That leader election takes about 20s, it is still possible for ScanRegion timeout given the 25s total retry time.
|
ti-chi-bot
pushed a commit
that referenced
this issue
May 23, 2022
This was referenced May 23, 2022
ti-chi-bot
added a commit
that referenced
this issue
May 24, 2022
overvenus
added a commit
to overvenus/ticdc
that referenced
this issue
Jun 20, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 20, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 20, 2022
ti-chi-bot
added a commit
that referenced
this issue
Jun 20, 2022
/label affects-5.4 |
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to overvenus/ticdc
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to overvenus/ticdc
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 23, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 23, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Jun 23, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Jun 23, 2022
/found customer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-4.0
affects-5.0
affects-5.1
affects-5.2
affects-5.3
affects-5.4
affects-6.0
affects-6.1
area/ticdc
Issues or PRs related to TiCDC.
component/kv-client
TiKV kv log client component.
report/customer
Customers have encountered this bug.
severity/moderate
type/bug
The issue is confirmed as a bug.
What did you do?
Run tpcc prepare on 4 node TiKV cluster. Create a changefeed to replication upstream write.
What did you expect to see?
No replication interruption.
What did you see instead?
Replication is interrupted due to following errors, which is caused by tikv/tikv#12410
tiflow/cdc/kv/client.go
Lines 930 to 967 in c6966a4
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):4.0.15
Upstream TiKV version (execute
tikv-server --version
):4.0.15
TiCDC version (execute
cdc version
):4.0.15
The text was updated successfully, but these errors were encountered: