From 81d6c8497c29019b3ae32ecc957d6a021e876e53 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Fri, 20 Dec 2024 18:39:21 +0800 Subject: [PATCH 1/2] add warnings for CentOS 7 usage (#19752) (#19753) --- hardware-and-software-requirements.md | 12 ++++++++---- releases/release-8.4.0.md | 6 +++--- releases/release-8.5.0.md | 7 +++++++ upgrade-tidb-using-tiup.md | 11 ++++++----- 4 files changed, 24 insertions(+), 12 deletions(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 0c4cff1f76bc1..785e7e6525384 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -89,14 +89,18 @@ This document describes the software and hardware requirements for deploying and +> **Warning:** +> +> - According to [CentOS Linux EOL](https://www.centos.org/centos-linux-eol/), the upstream support for CentOS Linux 7 ends on June 30, 2024. TiDB ends the support for CentOS 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on CentOS 7 to v8.4.0 or later will cause the cluster to become unavailable. Before upgrading TiDB, make sure to check your operating system version. +> - According to [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates), the maintenance support for Red Hat Enterprise Linux 7 ends on June 30, 2024. TiDB ends the support for Red Hat Enterprise Linux 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on Red Hat Enterprise Linux 7 to v8.4.0 or later will cause the cluster to become unavailable. Before upgrading TiDB, make sure to check your operating system version. +> - If you are using the 32-bit version of an operating system listed in the preceding table, TiDB **is not guaranteed** to be compilable, buildable or deployable on the 32-bit operating system and the corresponding CPU architecture, or TiDB does not actively adapt to the 32-bit operating system. +> - Other operating system versions not mentioned above might work but are not officially supported. + > **Note:** > > - For Oracle Enterprise Linux, TiDB supports the Red Hat Compatible Kernel (RHCK) and does not support the Unbreakable Enterprise Kernel provided by Oracle Enterprise Linux. -> - According to [CentOS Linux EOL](https://www.centos.org/centos-linux-eol/), the upstream support for CentOS Linux 7 ends on June 30, 2024. TiDB ends the support for CentOS 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. While the upstream support for CentOS Linux 8 ends on December 31, 2021, CentOS Stream 8 continues to be supported by the CentOS organization. -> - According to [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates), the maintenance support for Red Hat Enterprise Linux 7 ends on June 30, 2024. TiDB ends the support for Red Hat Enterprise Linux 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. +> - While the upstream support for CentOS Linux 8 ends on December 31, 2021, CentOS Stream 8 continues to be supported by the CentOS organization. > - Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended. -> - If you are using the 32-bit version of an operating system listed in the preceding table, TiDB **is not guaranteed** to be compilable, buildable or deployable on the 32-bit operating system and the corresponding CPU architecture, or TiDB does not actively adapt to the 32-bit operating system. -> - Other operating system versions not mentioned above might work but are not officially supported. > - Starting from v8.4.0, TiDB requires glibc 2.28. If your glibc version does not meet this requirement, it is recommended to use an operating system listed in the preceding table or upgrade the operating system to a version that supports glibc 2.28. ### Libraries required for compiling and running TiDB diff --git a/releases/release-8.4.0.md b/releases/release-8.4.0.md index feeccdd3b9ac3..68799d8398347 100644 --- a/releases/release-8.4.0.md +++ b/releases/release-8.4.0.md @@ -338,10 +338,10 @@ Starting from v8.4.0, the following contents are removed from the `TiDB-communit ## Operating system and platform requirement changes -- According to [CentOS Linux EOL](https://www.centos.org/centos-linux-eol/), the upstream support for CentOS Linux 7 ends on June 30, 2024. TiDB ends the support for CentOS 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. -- According to [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates), the maintenance support for Red Hat Enterprise Linux 7 ends on June 30, 2024. TiDB ends the support for Red Hat Enterprise Linux 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. +Before upgrading TiDB, ensure that your operating system version meets the [OS and platform requirements](/hardware-and-software-requirements.md#os-and-platform-requirements). -For the supported operating systems and platforms, see [Software and hardware recommendations](/hardware-and-software-requirements.md#os-and-platform-requirements). +- According to [CentOS Linux EOL](https://www.centos.org/centos-linux-eol/), the upstream support for CentOS Linux 7 ends on June 30, 2024. TiDB ends the support for CentOS 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on CentOS 7 to v8.4.0 or later will cause the cluster to become unavailable. +- According to [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates), the maintenance support for Red Hat Enterprise Linux 7 ends on June 30, 2024. TiDB ends the support for Red Hat Enterprise Linux 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on Red Hat Enterprise Linux 7 to v8.4.0 or later will cause the cluster to become unavailable. ## Removed features diff --git a/releases/release-8.5.0.md b/releases/release-8.5.0.md index 76833d49eb0a7..fe97f89dd1263 100644 --- a/releases/release-8.5.0.md +++ b/releases/release-8.5.0.md @@ -239,6 +239,13 @@ Compared with the previous LTS 8.1.0, 8.5.0 includes new features, improvements, | PD | [`patrol-region-worker-count`](/pd-configuration-file.md#patrol-region-worker-count-new-in-v850) | Newly added | Controls the number of concurrent [operators](/glossary.md#operator) created by the checker when inspecting the health state of a Region. | | BR | [`--checksum`](/br/br-snapshot-manual.md) | Modified | Changes the default value from `true` to `false`, meaning that BR does not calculate the table-level checksum during full backups by default, to improve backup performance. | +## Operating system and platform requirement changes + +Before upgrading TiDB, ensure that your operating system version meets the [OS and platform requirements](/hardware-and-software-requirements.md#os-and-platform-requirements). + +- According to [CentOS Linux EOL](https://www.centos.org/centos-linux-eol/), the upstream support for CentOS Linux 7 ends on June 30, 2024. TiDB ends the support for CentOS 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on CentOS 7 to v8.4.0 or later will cause the cluster to become unavailable. +- According to [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates), the maintenance support for Red Hat Enterprise Linux 7 ends on June 30, 2024. TiDB ends the support for Red Hat Enterprise Linux 7 starting from the 8.4 DMR version. It is recommended to use Rocky Linux 9.1 or a later version. Upgrading a TiDB cluster on Red Hat Enterprise Linux 7 to v8.4.0 or later will cause the cluster to become unavailable. + ## Removed features * The following feature has been removed: diff --git a/upgrade-tidb-using-tiup.md b/upgrade-tidb-using-tiup.md index 410e1013327ec..a6b61e2467058 100644 --- a/upgrade-tidb-using-tiup.md +++ b/upgrade-tidb-using-tiup.md @@ -10,11 +10,12 @@ This document applies to upgrading to TiDB v8.5.0 from the following versions: v > **Warning:** > -> 1. You cannot upgrade TiFlash online from versions earlier than 5.3 to 5.3 or later. Instead, you must first stop all the TiFlash instances of the early version, and then upgrade the cluster offline. If other components (such as TiDB and TiKV) do not support an online upgrade, follow the instructions in warnings in [Online upgrade](#online-upgrade). -> 2. **DO NOT** run DDL statements during the upgrade process. Otherwise, the issue of undefined behavior might occur. -> 3. **DO NOT** upgrade a TiDB cluster when a DDL statement is being executed in the cluster (usually for the time-consuming DDL statements such as `ADD INDEX` and the column type changes). Before the upgrade, it is recommended to use the [`ADMIN SHOW DDL`](/sql-statements/sql-statement-admin-show-ddl.md) command to check whether the TiDB cluster has an ongoing DDL job. If the cluster has a DDL job, to upgrade the cluster, wait until the DDL execution is finished or use the [`ADMIN CANCEL DDL`](/sql-statements/sql-statement-admin-cancel-ddl.md) command to cancel the DDL job before you upgrade the cluster. -> 4. If the TiDB version before upgrade is 7.1.0 or later, you can ignore the preceding warnings 2 and 3. For more information, see [limitations on using TiDB smooth upgrade](/smooth-upgrade-tidb.md#limitations). -> 5. Be sure to read [limitations on user operations](/smooth-upgrade-tidb.md#limitations-on-user-operations) before upgrading your TiDB cluster using TiUP. +> 1. Starting from v8.4.0, TiDB no longer supports CentOS 7 and Red Hat Enterprise Linux 7. It is recommended to use Rocky Linux 9.1 or later. Upgrading a TiDB cluster running on CentOS 7 or Red Hat Enterprise Linux 7 to v8.4.0 or later will cause the cluster to become unavailable. Before upgrading TiDB, ensure that your operating system version meets the [OS and platform requirements](/hardware-and-software-requirements.md#os-and-platform-requirements). +> 2. You cannot upgrade TiFlash online from versions earlier than 5.3 to 5.3 or later. Instead, you must first stop all the TiFlash instances of the early version, and then upgrade the cluster offline. If other components (such as TiDB and TiKV) do not support an online upgrade, follow the instructions in warnings in [Online upgrade](#online-upgrade). +> 3. **DO NOT** run DDL statements during the upgrade process. Otherwise, the issue of undefined behavior might occur. +> 4. **DO NOT** upgrade a TiDB cluster when a DDL statement is being executed in the cluster (usually for the time-consuming DDL statements such as `ADD INDEX` and the column type changes). Before the upgrade, it is recommended to use the [`ADMIN SHOW DDL`](/sql-statements/sql-statement-admin-show-ddl.md) command to check whether the TiDB cluster has an ongoing DDL job. If the cluster has a DDL job, to upgrade the cluster, wait until the DDL execution is finished or use the [`ADMIN CANCEL DDL`](/sql-statements/sql-statement-admin-cancel-ddl.md) command to cancel the DDL job before you upgrade the cluster. +> 5. If the TiDB version before upgrade is 7.1.0 or later, you can ignore the preceding warnings 3 and 4. For more information, see [limitations on using TiDB smooth upgrade](/smooth-upgrade-tidb.md#limitations). +> 6. Be sure to read [limitations on user operations](/smooth-upgrade-tidb.md#limitations-on-user-operations) before upgrading your TiDB cluster using TiUP. > **Note:** > From 14c73be54e2032591cf8a640313b3ca8909cb835 Mon Sep 17 00:00:00 2001 From: Suhaha Date: Fri, 20 Dec 2024 18:52:48 +0800 Subject: [PATCH 2/2] update(ci): ja translation (#19754) --- .github/workflows/cron.yml | 106 +++++++++--------- .../workflows/ja-full-translation-google.yaml | 2 +- 2 files changed, 54 insertions(+), 54 deletions(-) diff --git a/.github/workflows/cron.yml b/.github/workflows/cron.yml index dbcc5d41a2b67..d5796a4d17b46 100644 --- a/.github/workflows/cron.yml +++ b/.github/workflows/cron.yml @@ -63,63 +63,63 @@ jobs: git commit -m "update translated files" git push -# When ja-kernal version is different with cloud, open the comment and run the github action! -# ja-cloud: -# runs-on: ubuntu-latest + # When ja-kernal version is different with cloud, open the comment and run the github action! + # ja-cloud: + # runs-on: ubuntu-latest -# steps: -# - uses: actions/checkout@v4 -# name: Download translator repo -# with: -# repository: "shczhen/markdown-translator" -# path: "markdown-translator" -# - uses: actions/checkout@v4 -# name: Download docs repo and specified branch -# with: -# ref: "i18n-ja-release-7.1" -# path: "docs" -# - uses: actions/setup-node@v4 -# name: Setup node 18 -# with: -# node-version: 18 + # steps: + # - uses: actions/checkout@v4 + # name: Download translator repo + # with: + # repository: "shczhen/markdown-translator" + # path: "markdown-translator" + # - uses: actions/checkout@v4 + # name: Download docs repo and specified branch + # with: + # ref: "i18n-ja-release-7.1" + # path: "docs" + # - uses: actions/setup-node@v4 + # name: Setup node 18 + # with: + # node-version: 18 -# - run: | -# sudo apt install tree -y + # - run: | + # sudo apt install tree -y -# - name: Download files by comparing commits -# run: | -# export GH_TOKEN=${{github.token}} -# cd docs -# npm i -# node scripts/filterUpdateFiles.js -# tree tmp -# cd .. -# - name: Copy new files to translator folder -# run: | -# cp -r docs/tmp markdown-translator/markdowns -# - name: Config and translate -# run: | -# cd markdown-translator -# echo ${{secrets.GCP_KEY}} | base64 --decode >> key.json -# export GOOGLE_APPLICATION_CREDENTIALS=key.json -# export PROJECT_ID=${{ secrets.GCP_PROJECT_ID }} -# export GLOSSARY_ID=${{ secrets.GCP_GLOSSARY_ID }} -# yarn -# node src/index.js -# cd .. -# - name: Copy translated files to docs repo -# run: | -# cp -r markdown-translator/output/markdowns/* docs/ + # - name: Download files by comparing commits + # run: | + # export GH_TOKEN=${{github.token}} + # cd docs + # npm i + # node scripts/filterUpdateFiles.js + # tree tmp + # cd .. + # - name: Copy new files to translator folder + # run: | + # cp -r docs/tmp markdown-translator/markdowns + # - name: Config and translate + # run: | + # cd markdown-translator + # echo ${{secrets.GCP_KEY}} | base64 --decode >> key.json + # export GOOGLE_APPLICATION_CREDENTIALS=key.json + # export PROJECT_ID=${{ secrets.GCP_PROJECT_ID }} + # export GLOSSARY_ID=${{ secrets.GCP_GLOSSARY_ID }} + # yarn + # node src/index.js + # cd .. + # - name: Copy translated files to docs repo + # run: | + # cp -r markdown-translator/output/markdowns/* docs/ -# - name: Git commit and push -# run: | -# cd docs -# git status -# git config user.name github-actions -# git config user.email github-actions@github.com -# git add . -# git commit -m "update translated files" -# git push + # - name: Git commit and push + # run: | + # cd docs + # git status + # git config user.name github-actions + # git config user.email github-actions@github.com + # git add . + # git commit -m "update translated files" + # git push dispatch: runs-on: ubuntu-latest needs: [ja] diff --git a/.github/workflows/ja-full-translation-google.yaml b/.github/workflows/ja-full-translation-google.yaml index 89757a625ee7c..d2c630dc8790a 100644 --- a/.github/workflows/ja-full-translation-google.yaml +++ b/.github/workflows/ja-full-translation-google.yaml @@ -15,7 +15,7 @@ jobs: - uses: actions/checkout@v4 name: Download specified branch of docs repo with: - ref: "release-8.1" + ref: "release-8.5" path: "docs" - uses: actions/setup-node@v4 name: Setup node 18