-
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
fallback resolvedTs event skips the lock resolving unexpectly #3061
Labels
area/ticdc
Issues or PRs related to TiCDC.
component/kv-client
TiKV kv log client component.
severity/moderate
type/bug
The issue is confirmed as a bug.
Comments
2 tasks
maxshuang
changed the title
Also use
fallback resolvedTs event skips the lock resolving unexpectly
Oct 14, 2021
sinceLastEvent
as a check condition for lock resolving
maxshuang
added
severity/moderate
type/bug
The issue is confirmed as a bug.
component/kv-client
TiKV kv log client component.
labels
Oct 15, 2021
maxshuang
pushed a commit
that referenced
this issue
Oct 16, 2021
…ogress of resolveLock. close #3061
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
…ogress of resolveLock. close pingcap#3061
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
…ogress of resolveLock. close pingcap#3061
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
…ogress of resolveLock. close pingcap#3061
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
…ogress of resolveLock. close pingcap#3061
ti-chi-bot
pushed a commit
to ti-chi-bot/tiflow
that referenced
this issue
Oct 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ticdc
Issues or PRs related to TiCDC.
component/kv-client
TiKV kv log client component.
severity/moderate
type/bug
The issue is confirmed as a bug.
This bug is caused by following reason:
(1) when region merge occur, a new stream with new region_worker will be created. Then region_worker.rtsManager will be empty;
(2) if merged region has some fallback prewrite lock in it, the resolvedTs event will fall back last checkpointTs and will be ignored. Then resolve lock logic can't trigger for region_worker.rtsManager has no record for that region.
The text was updated successfully, but these errors were encountered: