Skip to content
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.

operate-schema set --flush may cause dm-worker server to restart #1730

Closed
glkappe opened this issue May 27, 2021 · 4 comments
Closed

operate-schema set --flush may cause dm-worker server to restart #1730

glkappe opened this issue May 27, 2021 · 4 comments
Labels
affected-v2.0.3 this issue/BUG affects v2.0.3 affected-v2.0.4 this issue/BUG affects v2.0.4 severity/moderate type/bug This issue is a bug report

Comments

@glkappe
Copy link

glkappe commented May 27, 2021

dm version:v2.0.3

operate-schema set --flush may cause dm-worker server to restart,This is an abnormal restart

dm-worker log:
{Because the operate-schema set --flush operation is executed multiple times, there are many restarts, and only the screenshot information of the restart is shown here.}

image

std error
stderr.txt

@GMHDBJD
Copy link
Collaborator

GMHDBJD commented May 27, 2021

#1724 (comment) It's a bug if we use --flush to create a table structure for fresh new tables

@lance6716 lance6716 added type/bug This issue is a bug report affected-v2.0.3 this issue/BUG affects v2.0.3 severity/moderate labels May 27, 2021
@glkappe
Copy link
Author

glkappe commented May 27, 2021

How to understand the definition of the new table, currently dm task is in sync state

@GMHDBJD
Copy link
Collaborator

GMHDBJD commented May 27, 2021

Syncer meet the table for the first time(no checkpoint for that table before)

@lance6716
Copy link
Collaborator

closed by #1799

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-v2.0.3 this issue/BUG affects v2.0.3 affected-v2.0.4 this issue/BUG affects v2.0.4 severity/moderate type/bug This issue is a bug report
Projects
None yet
Development

No branches or pull requests

3 participants