Skip to content

Commit 8fc5f0f

Browse files
qiancaiti-chi-bot
qiancai
authored and
ti-chi-bot
committed
This is an automated cherry-pick of pingcap#20020
Signed-off-by: ti-chi-bot <[email protected]>
1 parent 506234c commit 8fc5f0f

File tree

2 files changed

+104
-1
lines changed

2 files changed

+104
-1
lines changed

‎hardware-and-software-requirements.md

+103
Original file line numberDiff line numberDiff line change
@@ -96,12 +96,115 @@ This document describes the software and hardware requirements for deploying and
9696
> - 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.
9797
> - Other operating system versions not mentioned above might work but are not officially supported.
9898
99+
<<<<<<< HEAD
99100
> **Note:**
100101
>
101102
> - 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.
102103
> - While the upstream support for CentOS Linux 8 ends on December 31, 2021, CentOS Stream 8 continues to be supported by the CentOS organization.
103104
> - Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended.
104105
> - 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.
106+
=======
107+
<table>
108+
<thead>
109+
<tr>
110+
<th>Operating systems</th>
111+
<th>Supported CPU architectures</th>
112+
</tr>
113+
</thead>
114+
<tbody>
115+
<tr>
116+
<td>Red Hat Enterprise Linux 8.4 or a later 8.x version</td>
117+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
118+
</tr>
119+
<tr>
120+
<td>Amazon Linux 2</td>
121+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
122+
</tr>
123+
<tr>
124+
<td>Amazon Linux 2023</td>
125+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
126+
</tr>
127+
<tr>
128+
<td>Rocky Linux 9.1 or later</td>
129+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
130+
</tr>
131+
<tr>
132+
<td>Kylin Euler V10 SP1/SP2/SP3 (SP3 is supported starting from v7.5.5)</td>
133+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
134+
</tr>
135+
<tr>
136+
<td>UnionTech OS (UOS) V20</td>
137+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
138+
</tr>
139+
<tr>
140+
<td>openEuler 22.03 LTS SP1/SP3</td>
141+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
142+
</tr>
143+
</tbody>
144+
</table>
145+
146+
> **Warning:**
147+
>
148+
> - According to [CentOS Linux EOL](https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/), the upstream support for CentOS Linux 7 ended on June 30, 2024.
149+
> - Before upgrading TiDB, make sure to check your operating system version. TiDB v8.4.0 DMR and v8.5.0 removed the support of glibc 2.17, and dropped support and testing with CentOS Linux 7. 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 v8.5.0 will cause the risk of cluster unavailability.
150+
> - Starting from v8.5.1, to assist users still using CentOS Linux 7, TiDB resumes the support of glibc 2.17, resumes testing of CentOS Linux 7, and is now compatible with CentOS Linux 7. However, due to the EOL status of CentOS Linux, it is strongly recommended that you review the [official announcements and security guidance](https://www.redhat.com/en/blog/centos-linux-has-reached-its-end-life-eol) for CentOS Linux 7 and migrate to an operating system supported by TiDB for production use, such as Rocky Linux 9.1 or later.
151+
> - 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 ended 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.
152+
153+
+ For the following combinations of operating systems and CPU architectures, you can compile, build, and deploy TiDB. In addition, you can also use the basic features of OLTP, OLAP, and the data tools. However, TiDB **does not guarantee enterprise-level production quality**:
154+
155+
<table>
156+
<thead>
157+
<tr>
158+
<th>Operating systems</th>
159+
<th>Supported CPU architectures</th>
160+
</tr>
161+
</thead>
162+
<tbody>
163+
<tr>
164+
<td>macOS 12 (Monterey) or later</td>
165+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
166+
</tr>
167+
<tr>
168+
<td>Oracle Enterprise Linux 8 or a later</td>
169+
<td>x86_64</td>
170+
</tr>
171+
<tr>
172+
<td>Ubuntu LTS 20.04 or later</td>
173+
<td>x86_64</td>
174+
</tr>
175+
<tr>
176+
<td>CentOS Stream 8</td>
177+
<td><ul><li>x86_64</li><li>ARM 64</li></ul></td>
178+
</tr>
179+
<tr>
180+
<td>Debian 10 (Buster) or later</td>
181+
<td>x86_64</td>
182+
</tr>
183+
<tr>
184+
<td>Fedora 38 or later</td>
185+
<td>x86_64</td>
186+
</tr>
187+
<tr>
188+
<td>openSUSE Leap later than v15.5 (not including Tumbleweed)</td>
189+
<td>x86_64</td>
190+
</tr>
191+
<tr>
192+
<td>SUSE Linux Enterprise Server 15</td>
193+
<td>x86_64</td>
194+
</tr>
195+
</tbody>
196+
</table>
197+
198+
> **Note:**
199+
>
200+
> - 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.
201+
> - Support for Ubuntu 16.04 will be removed in future versions of TiDB. Upgrading to Ubuntu 18.04 or later is strongly recommended.
202+
> - CentOS Stream 8 reaches [End of Builds](https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/) on May 31, 2024.
203+
204+
+ If you are using the 32-bit version of an operating system listed in the preceding two tables, 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.
205+
206+
+ Other operating system versions not mentioned above might work but are not officially supported.
207+
>>>>>>> c05c781c69 (Update centos 7 on hardware-and-software-requirements.md (#20020))
105208
106209
### Libraries required for compiling and running TiDB
107210

‎upgrade-tidb-using-tiup.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ This document applies to upgrading to TiDB v8.5.0 from the following versions: v
1010

1111
> **Warning:**
1212
>
13-
> 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).
13+
> 1. Before upgrading TiDB, ensure that your operating system version meets the [OS and platform requirements](/hardware-and-software-requirements.md#os-and-platform-requirements). If you plan to upgrade your cluster running on CentOS Linux 7 to v8.5, ensure you use TiDB v8.5.1 or a later version to avoid the risk of cluster unavailability. For more information, see [TiDB v8.5.1 Release Notes](/releases/release-8.5.1.md).
1414
> 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).
1515
> 3. **DO NOT** run DDL statements during the upgrade process. Otherwise, the issue of undefined behavior might occur.
1616
> 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.

0 commit comments

Comments
 (0)