-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ticdc: update troubleshoot for ddl skip #6331
Conversation
Co-authored-by: TomShawn <[email protected]>
ticdc/troubleshoot-ticdc.md
Outdated
@@ -311,9 +311,9 @@ TiCDC 对大事务(大小超过 5 GB)提供部分支持,根据场景不同 | |||
## 当 changefeed 的下游为类 MySQL 数据库时,TiCDC 执行了一个耗时较长的 DDL 语句,阻塞了所有其他 changefeed,应该怎样处理? | |||
|
|||
1. 首先暂停执行耗时较长的 DDL 的 changefeed。此时可以观察到,这个 changefeed 暂停后,其他的 changefeed 不再阻塞了。 | |||
2. 在 TiCDC log 中搜寻 `apply job` 字段,确认耗时较长的 DDL 的 `StartTs`。 | |||
2. 在 TiCDC log 中搜寻 `apply job` 字段,确认耗时较长的 DDL 的 `start-ts`。如果旧版本的 TiCDC 没有打印该 `start-ts`,可以查询 TiDB DDL history,找到该条 DDL 语句的 `binlog.TableInfo.update_timestamp` 字段,该字段即为所需的 `start-ts`。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. 在 TiCDC log 中搜寻 `apply job` 字段,确认耗时较长的 DDL 的 `start-ts`。如果旧版本的 TiCDC 没有打印该 `start-ts`,可以查询 TiDB DDL history,找到该条 DDL 语句的 `binlog.TableInfo.update_timestamp` 字段,该字段即为所需的 `start-ts`。 | |
2. 在 TiCDC log 中搜寻 `apply job` 字段,确认耗时较长的 DDL 的 `start-ts`。如果旧版本(<= v4.0.13 或 <= v5.0.1)的 TiCDC 没有打印该 `start-ts`,可以查询 TiDB DDL history,找到该条 DDL 语句的 `binlog.TableInfo.update_timestamp` 字段,该字段即为所需的 `start-ts`。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL @TomShawn
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dev 版是最新开发版,应该不存在这个“旧版本”的历史问题。要不在 dev 中去掉“如果旧版本的 TiCDC 没有打印”这一句,在 release-x.0 文档中加上?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
可以
ptal @TomShawn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 46517fa
|
In response to a cherrypick label: new pull request created: #6334. |
In response to a cherrypick label: new pull request created: #6335. |
/translation done |
In response to a cherrypick label: new pull request could not be created: failed to create pull request against pingcap/docs-cn#release-4.0 from head ti-chi-bot:cherry-pick-6331-to-release-4.0: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-6331-to-release-4.0."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} |
Signed-off-by: ti-chi-bot <[email protected]>
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
ref: https://github.com/pingcap/ticdc/pull/1835
Add more instructions about how to find
start-ts
when cdc log doesn't contain it.Do your changes match any of the following descriptions?