From 898b56d1cbb4a773a5144fe8476790951dc9aeb3 Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 22 May 2020 18:58:55 +0800 Subject: [PATCH 1/7] finish the translation before the third subtitle --- ticdc/troubleshoot-ticdc.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 ticdc/troubleshoot-ticdc.md diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md new file mode 100644 index 0000000000000..13de933d0360e --- /dev/null +++ b/ticdc/troubleshoot-ticdc.md @@ -0,0 +1,23 @@ +--- +title: Common Problems and Troubleshooting +summary: Fix common problems while using TiCDC. +category: reference +aliases: ['/docs/dev/reference/tools/ticdc/troubleshoot-ticdc/'] +--- + +# Common Problems and Troubleshooting + +This document lists some common problems while using TiCDC and gives appropriate solutions. It also summarizes some common operation failures and ways to fix them. + +## How to choose start-ts while starting a task + +First, you should know that the `start-ts` of a replication task corresponds to a TSO of the upstream TiDB cluster. The replication task will start its data request from this TSO. Therefore, the `start-ts` should meet two conditions below: + +- The value of `start-ts` should be larger than current `tikv_gc_safe_point`, otherwise, an error would occur when creating the task. +- While starting the task, you should ensure that the downstream has all the data before `start-ts`. You can relax this requirement accordingly, if the replication task is for message queue or other scenarios, in which strict data consistency between upstream and downstream is not strictly required. + +If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets started, it will get the current TSO from PD and start to replicate data from this TSO. + +## When a task gets started, it prompts that some tables cannot be synchronized + +When using `cdc cli changefeed create` to create a replication task, it will check if the upstream tables comply with the [restrictions](/ticdc/ticdc-overview.md#restrictions). If there are tables , it will prompt that `some tables are not eligible to replicate` and list out the ineligible tables. If you choose `Y` or `y`, you will continue creating the replication task and automatically ignore all the updates of these ineligible tables. If you choose other inputs, the replication task will not be created. From 1b74c486e9946634a77cb76cfeb81fae96bb2356 Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 22 May 2020 19:06:23 +0800 Subject: [PATCH 2/7] Update troubleshoot-ticdc.md --- ticdc/troubleshoot-ticdc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md index 13de933d0360e..eef5d3284f247 100644 --- a/ticdc/troubleshoot-ticdc.md +++ b/ticdc/troubleshoot-ticdc.md @@ -18,6 +18,6 @@ First, you should know that the `start-ts` of a replication task corresponds to If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets started, it will get the current TSO from PD and start to replicate data from this TSO. -## When a task gets started, it prompts that some tables cannot be synchronized +## When a task gets started, it prompts that some tables cannot be replicated When using `cdc cli changefeed create` to create a replication task, it will check if the upstream tables comply with the [restrictions](/ticdc/ticdc-overview.md#restrictions). If there are tables , it will prompt that `some tables are not eligible to replicate` and list out the ineligible tables. If you choose `Y` or `y`, you will continue creating the replication task and automatically ignore all the updates of these ineligible tables. If you choose other inputs, the replication task will not be created. From cb7ed0ce1dcb110ff29319843526cef6464ba987 Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 22 May 2020 19:27:30 +0800 Subject: [PATCH 3/7] Update troubleshoot-ticdc.md --- ticdc/troubleshoot-ticdc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md index eef5d3284f247..af58a9c2606e6 100644 --- a/ticdc/troubleshoot-ticdc.md +++ b/ticdc/troubleshoot-ticdc.md @@ -20,4 +20,4 @@ If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets s ## When a task gets started, it prompts that some tables cannot be replicated -When using `cdc cli changefeed create` to create a replication task, it will check if the upstream tables comply with the [restrictions](/ticdc/ticdc-overview.md#restrictions). If there are tables , it will prompt that `some tables are not eligible to replicate` and list out the ineligible tables. If you choose `Y` or `y`, you will continue creating the replication task and automatically ignore all the updates of these ineligible tables. If you choose other inputs, the replication task will not be created. +When using `cdc cli changefeed create` to create a replication task, it will check if the upstream tables comply with the [restrictions](/ticdc/ticdc-overview.md#restrictions). If not, it will prompt that `some tables are not eligible to replicate` and list out the ineligible tables. If you choose `Y` or `y`, you will continue creating the replication task and automatically ignore all the updates of these ineligible tables. If you choose other inputs, the replication task will not be created. From c6e289856718acec8e974859d746a8a49c18e46a Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 22 May 2020 19:37:23 +0800 Subject: [PATCH 4/7] Update troubleshoot-ticdc.md --- ticdc/troubleshoot-ticdc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md index af58a9c2606e6..7d883fccd0df4 100644 --- a/ticdc/troubleshoot-ticdc.md +++ b/ticdc/troubleshoot-ticdc.md @@ -14,7 +14,7 @@ This document lists some common problems while using TiCDC and gives appropriate First, you should know that the `start-ts` of a replication task corresponds to a TSO of the upstream TiDB cluster. The replication task will start its data request from this TSO. Therefore, the `start-ts` should meet two conditions below: - The value of `start-ts` should be larger than current `tikv_gc_safe_point`, otherwise, an error would occur when creating the task. -- While starting the task, you should ensure that the downstream has all the data before `start-ts`. You can relax this requirement accordingly, if the replication task is for message queue or other scenarios, in which strict data consistency between upstream and downstream is not strictly required. +- While starting the task, you should ensure that the downstream has already got all the data previous to `start-ts`. You can relax this requirement accordingly, if the replication task is for message queue or other scenarios, in which strict data consistency between upstream and downstream is not strictly required. If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets started, it will get the current TSO from PD and start to replicate data from this TSO. From c32fc013ccd348481f692231eb51f5a605d09367 Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 22 May 2020 19:38:51 +0800 Subject: [PATCH 5/7] Update troubleshoot-ticdc.md --- ticdc/troubleshoot-ticdc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md index 7d883fccd0df4..f3dee07ff2525 100644 --- a/ticdc/troubleshoot-ticdc.md +++ b/ticdc/troubleshoot-ticdc.md @@ -16,7 +16,7 @@ First, you should know that the `start-ts` of a replication task corresponds to - The value of `start-ts` should be larger than current `tikv_gc_safe_point`, otherwise, an error would occur when creating the task. - While starting the task, you should ensure that the downstream has already got all the data previous to `start-ts`. You can relax this requirement accordingly, if the replication task is for message queue or other scenarios, in which strict data consistency between upstream and downstream is not strictly required. -If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets started, it will get the current TSO from PD and start to replicate data from this TSO. +If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets started, it will get the current TSO from PD and start to replicate data from it. ## When a task gets started, it prompts that some tables cannot be replicated From 01abcdc383785ca8662434596ac11f36d36fca66 Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 22 May 2020 19:47:11 +0800 Subject: [PATCH 6/7] Update troubleshoot-ticdc.md --- ticdc/troubleshoot-ticdc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md index f3dee07ff2525..a100ab291a96c 100644 --- a/ticdc/troubleshoot-ticdc.md +++ b/ticdc/troubleshoot-ticdc.md @@ -7,7 +7,7 @@ aliases: ['/docs/dev/reference/tools/ticdc/troubleshoot-ticdc/'] # Common Problems and Troubleshooting -This document lists some common problems while using TiCDC and gives appropriate solutions. It also summarizes some common operation failures and ways to fix them. +This document includes some common problems while using TiCDC and appropriate solutions. It also summarizes some common operation failures and ways to fix them. ## How to choose start-ts while starting a task From a33552e6fe67408dc31dce64669faaaa58ac3593 Mon Sep 17 00:00:00 2001 From: Anastasia-Lu <44253319+Anastasia-Lu@users.noreply.github.com> Date: Fri, 29 May 2020 11:06:31 +0800 Subject: [PATCH 7/7] correct grammar mistakes --- ticdc/troubleshoot-ticdc.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/ticdc/troubleshoot-ticdc.md b/ticdc/troubleshoot-ticdc.md index a100ab291a96c..a8e5a4dfc1b13 100644 --- a/ticdc/troubleshoot-ticdc.md +++ b/ticdc/troubleshoot-ticdc.md @@ -2,22 +2,21 @@ title: Common Problems and Troubleshooting summary: Fix common problems while using TiCDC. category: reference -aliases: ['/docs/dev/reference/tools/ticdc/troubleshoot-ticdc/'] --- # Common Problems and Troubleshooting -This document includes some common problems while using TiCDC and appropriate solutions. It also summarizes some common operation failures and ways to fix them. +This document includes some common problems that you might have while using TiCDC and provides appropriate solutions. It also summarizes some common operation failures and ways to fix them. ## How to choose start-ts while starting a task -First, you should know that the `start-ts` of a replication task corresponds to a TSO of the upstream TiDB cluster. The replication task will start its data request from this TSO. Therefore, the `start-ts` should meet two conditions below: +First, you need to know that the `start-ts` of a replication task corresponds to a TSO of the upstream TiDB cluster. The replication task will start its data request from this TSO. Therefore, the `start-ts` should meet two conditions below: -- The value of `start-ts` should be larger than current `tikv_gc_safe_point`, otherwise, an error would occur when creating the task. -- While starting the task, you should ensure that the downstream has already got all the data previous to `start-ts`. You can relax this requirement accordingly, if the replication task is for message queue or other scenarios, in which strict data consistency between upstream and downstream is not strictly required. +- The value of `start-ts` must be larger than current `tikv_gc_safe_point`, otherwise, an error would occur when creating the task. +- While starting a task, you need to ensure that the downstream has already got all the data previous to `start-ts`. You can relax this requirement accordingly, if the replication task is for message queue or other scenarios, in which strict data consistency between upstream and downstream is not strictly required. -If `start-ts` is not specified or specified 0 `start-ts=0`, when the task gets started, it will get the current TSO from PD and start to replicate data from it. +If `start-ts` is not specified or specified as `0`, when a replication task gets started, TiCDC will get the current TSO from PD and start to replicate data from it. ## When a task gets started, it prompts that some tables cannot be replicated -When using `cdc cli changefeed create` to create a replication task, it will check if the upstream tables comply with the [restrictions](/ticdc/ticdc-overview.md#restrictions). If not, it will prompt that `some tables are not eligible to replicate` and list out the ineligible tables. If you choose `Y` or `y`, you will continue creating the replication task and automatically ignore all the updates of these ineligible tables. If you choose other inputs, the replication task will not be created. +When you use `cdc cli changefeed create` to create a replication task, TiCDC will check if the upstream tables comply with the [restrictions](/ticdc/ticdc-overview.md#restrictions). If they don't, TiCDC will prompt that `some tables are not eligible to replicate`, and will list out the ineligible tables. If you choose `Y` or `y`, TiCDC will continue creating the replication task and automatically ignore all the updates of these ineligible tables. If you choose other inputs, the replication task will not be created.