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.

Sign up for GitHub

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

Jump to bottom

redo log: change stuck in case redo_apply_multiple_workload_node_restart_sync #6695

Closed
Tammyxia opened this issue Aug 10, 2022 · 2 comments · Fixed by #6671
Closed

redo log: change stuck in case redo_apply_multiple_workload_node_restart_sync #6695

Tammyxia opened this issue Aug 10, 2022 · 2 comments · Fixed by #6671
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.

Comments

@Tammyxia
Copy link

What did you do?

  • create changefeed1: enable redo log, filter sysbench table
  • create changefeed2: enable redo log, filter go-ycsb table
  • run sysbench prepare, meanwhile, all cdc node restart
  • run truncate all sysbench table
  • run sysbench run, meanwhile, all pd restart
  • drop all sysbench tables
  • run sysbench prepare again
  • run go-ycsb workload
  • sendfinishmark and waitforthisDDL

What did you expect to see?

No response

What did you see instead?

k0JvrUqnLJ

Versions of the cluster

Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):

(paste TiKV version here)

TiCDC version (execute cdc version):

(paste TiCDC version here)
Release Version: v6.1.0-20220809
Git Commit Hash: 0c82c3405e49ac1da9f5e705d3862ec5a79c22bf
Git Branch: heads/refs/tags/v6.1.0-20220809
UTC Build Time: 2022-08-09 13:29:30
Go Version: go version go1.18.5 linux/amd64
Failpoint Build: false
@Tammyxia Tammyxia added type/bug The issue is confirmed as a bug. area/ticdc Issues or PRs related to TiCDC. severity/major labels Aug 10, 2022
@nongfushanquan
Copy link
Contributor

#6671

@hicqu
Copy link
Contributor

hicqu commented Aug 12, 2022

/remove-label may-affects-4.0
/remove-label may-affects-5.0
/remove-label may-affects-5.1
/remove-label may-affects-5.2
/remove-label may-affects-5.3
/remove-label may-affects-5.4
/remove-label may-affects-6.0
/remove-label may-affects-6.1
/remove-label may-affects-6.2
/label affects-6.1
/label affects-6.2

This was referenced Aug 12, 2022
Closed
Merged
ti-chi-bot pushed a commit that referenced this issue Aug 12, 2022
@hicqu
redo(ticdc): owner and processores shouldn't share one redo log writer (
fa7cd9a 
#6671)

close #6695
This was referenced Aug 12, 2022
Merged
Closed
Merged
ti-chi-bot added a commit that referenced this issue Aug 12, 2022
@ti-chi-bot
redo(ticdc): owner and processores shouldn't share one redo log writer (
b3cd5a4 
#6671) (#6731)

close #6695
hicqu added a commit to ti-chi-bot/tiflow that referenced this issue Aug 16, 2022
@hicqu
redo(ticdc): owner and processores shouldn't share one redo log writer (
7687432 
pingcap#6671)

close pingcap#6695

Signed-off-by: qupeng <[email protected]>
ti-chi-bot added a commit that referenced this issue Aug 17, 2022
@ti-chi-bot
redo(ticdc): owner and processores shouldn't share one redo log writer (
e0bc0f7 
#6671) (#6729)

close #6695
This was referenced Aug 29, 2022
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

redo(ticdc): owner and processores shouldn't share one redo log writer hicqu/ticdc
4 participants
@hicqu @ti-chi-bot @Tammyxia @nongfushanquan