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

Unnormal conflict detect durations are not logged #11271

Closed
hicqu opened this issue Jun 7, 2024 · 0 comments · Fixed by #11251
Closed

Unnormal conflict detect durations are not logged #11271

hicqu opened this issue Jun 7, 2024 · 0 comments · Fixed by #11251
Assignees
@hicqu
Labels
affects-6.5 affects-7.1 affects-7.5 affects-8.1 area/ticdc Issues or PRs related to TiCDC. severity/minor type/enhancement The issue or PR belongs to an enhancement.

Comments

@hicqu
Copy link
Contributor

hicqu commented Jun 7, 2024

What did you do?

Unnormal conflict detect durations are not logged. It makes investigating relative problems harder.

What did you expect to see?

No response

What did you see instead?

Unnormal conflict detect durations are not logged. It makes investigating relative problems harder.

Versions of the cluster

All branches after 6.5.0.
@hicqu hicqu added type/bug The issue is confirmed as a bug. area/ticdc Issues or PRs related to TiCDC. severity/minor labels Jun 7, 2024
@hicqu hicqu mentioned this issue Jun 7, 2024
Merged
@flowbehappy flowbehappy added type/enhancement The issue or PR belongs to an enhancement. and removed type/bug The issue is confirmed as a bug. labels Jun 7, 2024
@ti-chi-bot ti-chi-bot bot closed this as completed in d662c77 Jun 11, 2024
ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this issue Jun 11, 2024
@hicqu @ti-chi-bot
cdc: log slow conflict detect every 60s (pingcap#11251)
4229e1b 
close pingcap#11271
This was referenced Jun 11, 2024
Open
Closed
ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this issue Jun 11, 2024
@hicqu @ti-chi-bot
cdc: log slow conflict detect every 60s (pingcap#11251)
56f10fb 
close pingcap#11271
@ti-chi-bot ti-chi-bot mentioned this issue Jun 11, 2024
Merged
ti-chi-bot pushed a commit to ti-chi-bot/tiflow that referenced this issue Jun 11, 2024
@hicqu @ti-chi-bot
cdc: log slow conflict detect every 60s (pingcap#11251)
664e17a 
close pingcap#11271
@ti-chi-bot ti-chi-bot mentioned this issue Jun 11, 2024
Merged
ti-chi-bot bot pushed a commit that referenced this issue Jun 11, 2024
@ti-chi-bot
cdc: log slow conflict detect every 60s (#11251) (#11287)
053cdaf 
close #11271
hicqu added a commit to ti-chi-bot/tiflow that referenced this issue Jun 12, 2024
@hicqu
Squashed commit of the following:
a3d30ca 
commit c092599
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 12 00:26:59 2024 +0800

    pkg/config, sink(ticdc): support output raw change event for mq and cloud storage sink (pingcap#11226) (pingcap#11290)

    close pingcap#11211

commit 3426e46
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 19:40:29 2024 +0800

    puller(ticdc): fix wrong update splitting behavior after table scheduling (pingcap#11269) (pingcap#11282)

    close pingcap#11219

commit 2a28078
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 16:40:37 2024 +0800

    mysql(ticdc): remove error filter when check isTiDB in backend init (pingcap#11214) (pingcap#11261)

    close pingcap#11213

commit 2425d54
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 16:40:30 2024 +0800

    log(ticdc): Add more error query information to the returned error to facilitate users to know the cause of the failure (pingcap#10945) (pingcap#11257)

    close pingcap#11254

commit 053cdaf
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 15:34:30 2024 +0800

    cdc: log slow conflict detect every 60s (pingcap#11251) (pingcap#11287)

    close pingcap#11271

commit 327ba7b
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Tue Jun 11 11:42:00 2024 +0800

    redo(ticdc): return internal error in redo writer (pingcap#11011) (pingcap#11091)

    close pingcap#10124

commit d82ae89
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Mon Jun 10 22:28:29 2024 +0800

    ddl_puller (ticdc): handle dorp pk/uk ddl correctly (pingcap#10965) (pingcap#10981)

    close pingcap#10890

commit f15bec9
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Fri Jun 7 16:16:28 2024 +0800

    redo(ticdc): enable pprof and set memory limit for redo applier (pingcap#10904) (pingcap#10996)

    close pingcap#10900

commit ba50a0e
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 5 19:58:26 2024 +0800

    test(ticdc): enable sequence test (pingcap#11023) (pingcap#11037)

    close pingcap#11015

commit 94b9897
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 5 17:08:56 2024 +0800

    mounter(ticdc): timezone fill default value should also consider tz. (pingcap#10932) (pingcap#10946)

    close pingcap#10931

commit a912d33
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed Jun 5 10:49:25 2024 +0800

    mysql (ticdc): Improve the performance of the mysql sink by refining the transaction event batching logic (pingcap#10466) (pingcap#11242)

    close pingcap#11241

commit 6277d9a
Author: dongmen <20351731+asddongmen@users.noreply.github.com>
Date:   Wed May 29 20:13:22 2024 +0800

    kvClient (ticdc): revert e5999e3 to remove useless metrics (pingcap#11184)

    close pingcap#11073

commit 54e93ed
Author: dongmen <20351731+asddongmen@users.noreply.github.com>
Date:   Wed May 29 17:43:22 2024 +0800

    syncpoint (ticdc): make syncpoint support base64 encoded password (pingcap#11162)

    close pingcap#10516

commit 0ba9329
Author: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Date:   Wed May 29 09:07:21 2024 +0800

    (redo)ticdc: fix the event orderliness in redo log (pingcap#11117) (pingcap#11180)

    close pingcap#11096

Signed-off-by: qupeng <qupeng@pingcap.com>
hicqu pushed a commit to hicqu/ticdc that referenced this issue Jun 13, 2024
@ti-chi-bot @hicqu
cdc: log slow conflict detect every 60s (pingcap#11251) (pingcap#11287)
0909617 
close pingcap#11271

Signed-off-by: qupeng <qupeng@pingcap.com>
ti-chi-bot bot pushed a commit that referenced this issue Jul 31, 2024
@ti-chi-bot
cdc: log slow conflict detect every 60s (#11251) (#11286)
739708f 
close #11271
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hicqu hicqu

Labels
affects-6.5 affects-7.1 affects-7.5 affects-8.1 area/ticdc Issues or PRs related to TiCDC. severity/minor type/enhancement The issue or PR belongs to an enhancement.
Projects
Question and Bug Reports
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

cdc: log slow conflict detect every 60s hicqu/ticdc
2 participants
@flowbehappy @hicqu