From b9ea2898f0d2f87fb2cd4216bc82e549758c12c7 Mon Sep 17 00:00:00 2001 From: JoyinQin <56883733+Joyinqin@users.noreply.github.com> Date: Fri, 10 Jul 2020 09:20:27 +0800 Subject: [PATCH 1/3] translate add-upgrade-faq --- faq/upgrade-faq.md | 36 ++++++++++++++++++++++++++---------- 1 file changed, 26 insertions(+), 10 deletions(-) diff --git a/faq/upgrade-faq.md b/faq/upgrade-faq.md index 62464bdc4e8f1..9a1f045064536 100644 --- a/faq/upgrade-faq.md +++ b/faq/upgrade-faq.md @@ -1,15 +1,31 @@ --- -title: FAQs After Upgrade -summary: Learn about the FAQs after upgrading TiDB. +title: FAQs Upgrade and After Upgrade +summary: Learn about some FAQs and their solutions during and after TiDB upgrade. category: faq aliases: ['/docs/dev/faq/upgrade-faq/','/docs/dev/faq/upgrade/'] --- -# FAQs After Upgrade +# FAQs about Upgrade and After Upgrade -This document lists some FAQs and their solutions after you upgrade TiDB. +This document introduces some FAQs and their solutions when or after you upgrade TiDB. -## The character set (charset) errors when executing DDL operations +## FAQs Upgrade + +This section lists some FAQs and their solutions when you upgrade TiDB. + +### How are the rolling updates done? + +When you apply rolling updates to the TiDB services, the running application is not affected. You need to configure the minimum cluster topology (TiDB \* 2, PD \* 3, TiKV \* 3). If the Pump/Drainer service is involved in the cluster, it is recommended to stop Drainer before rolling updates. When you update TiDB, Pump is also updated. + +### How to upgrade Binary + +It is not recommended to deploy TiDB using Binary. The support for upgrading using Binary is not as friendly as using TiUP. It is recommended to [deploy TiDB using TiUP](https://docs.pingcap.com/tidb/stable/production-deployment-using-tiup). + +## FAQs After Upgrade + +This section lists some FAQs and their solutions after you upgrade TiDB. + +### The character set (charset) errors when executing DDL operations In v2.1.0 and earlier versions (including all versions of v2.0), the character set of TiDB is UTF-8 by default. But starting from v2.1.1, the default character set has been changed into UTF8MB4. @@ -17,11 +33,11 @@ If you explicitly specify the charset of a newly created table as UTF-8 in v2.1. To avoid this issue, you need to pay attention to: -- Point #1: before v2.1.3, TiDB does not support modifying the charset of the column. Therefore, when you execute DDL operations, you need to make sure that the charset of the new column is consistent with that of the original column. +- Before v2.1.3, TiDB does not support modifying the charset of the column. Therefore, when you execute DDL operations, you need to make sure that the charset of the new column is consistent with that of the original column. -- Point #2: before v2.1.3, even if the charset of the column is different from that of the table, `show create table` does not show the charset of the column. But as shown in the following example, you can view it by obtaining the metadata of the table through the HTTP API. +- Before v2.1.3, even if the charset of the column is different from that of the table, `show create table` does not show the charset of the column. But as shown in the following example, you can view it by obtaining the metadata of the table through the HTTP API. -### Issue #1: `unsupported modify column charset utf8mb4 not match origin utf8` +#### `unsupported modify column charset utf8mb4 not match origin utf8` - Before upgrading, the following operations are executed in v2.1.0 and earlier versions. @@ -120,7 +136,7 @@ alter table t change column a a varchar(22) character set utf8; } ``` -### Issue #2: `unsupported modify charset from utf8mb4 to utf8` +#### `unsupported modify charset from utf8mb4 to utf8` - Before upgrading, the following operations are executed in v2.1.1 and v2.1.2. @@ -201,7 +217,7 @@ Solution: alter table t change column a a varchar(20) character set utf8mb4; ``` -### Issue #3: `ERROR 1366 (HY000): incorrect utf8 value f09f8c80(🌀) for column a` +#### `ERROR 1366 (HY000): incorrect utf8 value f09f8c80(🌀) for column a` In TiDB v2.1.1 and earlier versions, if the charset is UTF-8, there is no UTF-8 Unicode encoding check on the inserted 4-byte data. But in v2.1.2 and the later versions, this check is added. From 89670f29286903af72365e5c37a4054cb74f34bf Mon Sep 17 00:00:00 2001 From: JoyinQ <56883733+Joyinqin@users.noreply.github.com> Date: Fri, 10 Jul 2020 09:31:46 +0800 Subject: [PATCH 2/3] Update upgrade-faq.md --- faq/upgrade-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faq/upgrade-faq.md b/faq/upgrade-faq.md index 9a1f045064536..a1a54465dee99 100644 --- a/faq/upgrade-faq.md +++ b/faq/upgrade-faq.md @@ -5,7 +5,7 @@ category: faq aliases: ['/docs/dev/faq/upgrade-faq/','/docs/dev/faq/upgrade/'] --- -# FAQs about Upgrade and After Upgrade +# FAQs Upgrade and After Upgrade This document introduces some FAQs and their solutions when or after you upgrade TiDB. From 98199446e2fc76fe5a08239a7c13d6d4c6f48205 Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Fri, 17 Jul 2020 17:00:08 +0800 Subject: [PATCH 3/3] Apply suggestions from code review --- faq/upgrade-faq.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/faq/upgrade-faq.md b/faq/upgrade-faq.md index 0262d4199bb4c..add8cb45950b5 100644 --- a/faq/upgrade-faq.md +++ b/faq/upgrade-faq.md @@ -1,26 +1,26 @@ --- -title: FAQs Upgrade and After Upgrade -summary: Learn about some FAQs and their solutions during and after TiDB upgrade. +title: Upgrade and After Upgrade FAQs +summary: Learn about some FAQs and the solutions during and after upgrading TiDB. aliases: ['/docs/dev/faq/upgrade-faq/','/docs/dev/faq/upgrade/'] --- -# FAQs Upgrade and After Upgrade +# Upgrade and After Upgrade FAQs This document introduces some FAQs and their solutions when or after you upgrade TiDB. -## FAQs Upgrade +## Upgrade FAQs This section lists some FAQs and their solutions when you upgrade TiDB. -### How are the rolling updates done? +### What are the effects of rolling updates? -When you apply rolling updates to the TiDB services, the running application is not affected. You need to configure the minimum cluster topology (TiDB \* 2, PD \* 3, TiKV \* 3). If the Pump/Drainer service is involved in the cluster, it is recommended to stop Drainer before rolling updates. When you update TiDB, Pump is also updated. +When you apply rolling updates to the TiDB services, the running application is not affected. You need to configure the minimum cluster topology (TiDB \* 2, PD \* 3, TiKV \* 3). If the Pump or Drainer service is involved in the cluster, it is recommended to stop Drainer before rolling updates. When you upgrade TiDB, Pump is also upgraded. -### How to upgrade Binary +### How to upgrade TiDB using the binary? -It is not recommended to deploy TiDB using Binary. The support for upgrading using Binary is not as friendly as using TiUP. It is recommended to [deploy TiDB using TiUP](https://docs.pingcap.com/tidb/stable/production-deployment-using-tiup). +It is not recommended to deploy TiDB using the binary. The TiDB support for upgrading using Binary is not as friendly as using TiUP. It is recommended to [deploy TiDB using TiUP](/production-deployment-using-tiup.md). -## FAQs After Upgrade +## After upgrade FAQs This section lists some FAQs and their solutions after you upgrade TiDB.