From 5fba20d4379b0b3233fe0f820ad430f3a8fb5660 Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Tue, 26 Nov 2024 18:18:40 +0800 Subject: [PATCH 1/2] docs: refine docs to explain that cloudberry can also be deployed on virtual machines --- docs/cbdb-op-deploy-guide.md | 4 ++-- docs/cbdb-op-prepare-to-deploy.md | 4 ++-- docs/cbdb-op-software-hardware.md | 10 ++++---- .../current.json | 6 ++--- .../current/cbdb-op-deploy-guide.md | 24 +++++++++---------- .../current/cbdb-op-prepare-to-deploy.md | 4 ++-- .../current/cbdb-op-software-hardware.md | 10 ++++---- sidebars.ts | 2 +- 8 files changed, 34 insertions(+), 30 deletions(-) diff --git a/docs/cbdb-op-deploy-guide.md b/docs/cbdb-op-deploy-guide.md index 555658ded33..bb0dab32e60 100644 --- a/docs/cbdb-op-deploy-guide.md +++ b/docs/cbdb-op-deploy-guide.md @@ -4,7 +4,7 @@ title: Deploy Manually Using RPM Package # Deploy Cloudberry Database Manually Using RPM Package -This document introduces how to manually deploy Cloudberry Database on physical machines using RPM package. Before reading this document, it is recommended to first read the [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) and [Prepare to Deploy Cloudberry Database on Physical Machine](/docs/cbdb-op-prepare-to-deploy.md). +This document introduces how to manually deploy Cloudberry Database on physical/virtual machines using RPM package. Before reading this document, it is recommended to first read the [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) and [Prepare to Deploy Cloudberry Database](/docs/cbdb-op-prepare-to-deploy.md). The deployment method in this document is for production environments. @@ -18,7 +18,7 @@ The example in this document uses CentOS 7.6 and deploys Cloudberry Database v1. ## Step 1: Prepare server nodes -Read the [Prepare to Deploy Cloudberry Database on Physical Machine](/docs/cbdb-op-prepare-to-deploy.md) document to prepare the server nodes. +Read the [Prepare to Deploy Cloudberry Database](/docs/cbdb-op-prepare-to-deploy.md) document to prepare the server nodes. ## Step 2. Install the RPM package diff --git a/docs/cbdb-op-prepare-to-deploy.md b/docs/cbdb-op-prepare-to-deploy.md index d6c72f3df65..17c18223101 100644 --- a/docs/cbdb-op-prepare-to-deploy.md +++ b/docs/cbdb-op-prepare-to-deploy.md @@ -2,9 +2,9 @@ title: Prepare to Deploy --- -# Prepare to Deploy on Physical Machine +# Prepare to Deploy on Physical or Virtual Machine -Before deploying Cloudberry Database on physical machines, you need to do some preparations. Read this document and [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) before you start to deploy Cloudberry Database. +Before deploying Cloudberry Database on physical or virtual machines, you need to do some preparations. Read this document and [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) before you start to deploy Cloudberry Database. ## Plan the deployment architecture diff --git a/docs/cbdb-op-software-hardware.md b/docs/cbdb-op-software-hardware.md index 02d17f07095..a6678e4d9a3 100644 --- a/docs/cbdb-op-software-hardware.md +++ b/docs/cbdb-op-software-hardware.md @@ -4,13 +4,13 @@ title: Software and Hardware Configuration # Software and Hardware Configuration -This document introduces the software and hardware configuration required for Cloudberry Database. +This document introduces the software and hardware configuration required for Apache Cloudberry. ## Hardware requirements -### Physical machine +### Supported deployment environments -The following section describes the recommended physical machine configuration for Cloudberry Database in test and production environments. +Apache Cloudberry supports deployment on both physical machines and virtual machines. Below are the recommended configurations for the environments. #### For development or test environments @@ -30,6 +30,8 @@ The following section describes the recommended physical machine configuration f | ETCD | 16+ cores | 64+ GB | SSD | 10 Gbps NIC (2 preferred) | 3+ | | FTS | 4+ cores | 8+ GB | SSD | 10 Gbps NIC (2 preferred) | 3+ | +Apache Cloudberry can also be deployed on public cloud platforms such as AWS, Azure, and GCP. The hardware requirements for cloud-based deployments might vary based on the instance types selected on these platforms. Refer to the specific cloud provider’s documentation for instance configurations that meet or exceed the recommended hardware specifications. + ### Storage - To prevent a high data disk load from affecting the operating system's normal I/O response, mount the operating system and the data disk on separate disks. @@ -96,7 +98,7 @@ mount /dev/data/data2 /data2/ ### Supported OS -Cloudberry Database supports the following operating systems: +Apache Cloudberry supports the following operating systems: - Kylin V10 SP1 or SP2 - NeoKylin V7update6 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current.json b/i18n/zh/docusaurus-plugin-content-docs/current.json index fdd8ac78e8c..44453edf538 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current.json +++ b/i18n/zh/docusaurus-plugin-content-docs/current.json @@ -11,9 +11,9 @@ "message": "部署和构建", "description": "The label for category deployment guides in sidebar docs" }, - "sidebar.docsbars.category.Deploy on Physical Machine": { - "message": "物理机部署", - "description": "The label for category physical machine deployment guides in sidebar docs" + "sidebar.docsbars.category.Deploy on Physical or Virtual Machine": { + "message": "物理机/虚拟机部署", + "description": "The label for category physical/virtual machine deployment guides in sidebar docs" }, "sidebar.docsbars.category.Build from Source Code": { "message": "从源码编译安装", diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md index a9ffe503a4a..76b003c6812 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md @@ -2,13 +2,13 @@ title: 通过 RPM 包手动部署 --- -# 通过 RPM 包在物理机上手动部署 Cloudberry Database +# 通过 RPM 包手动部署 Apache Cloudberry -本文档介绍如何通过 RPM 包在物理机上安装与部署 Cloudberry Database。在阅读本文前，建议先阅读[软硬件配置需求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)和[物理机部署前准备工作](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md)。 +本文档介绍如何通过 RPM 包在物理机/虚拟机上安装与部署 Apache Cloudberry。在阅读本文前，建议先阅读[软硬件配置需求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)和[部署前准备工作](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md)。 本文所介绍的部署方法可用于生产环境。 -本文示例以 CentOS 7.6 为例，说明如何部署 Cloudberry Database v1.0.0。主要分为以下步骤： +本文示例以 CentOS 7.6 为例，说明如何部署 Apache Cloudberry v1.0.0。主要分为以下步骤： 1. [准备节点服务器](#第-1-步准备节点服务器)。 2. [安装 RPM 包](#第-2-步安装-rpm-包)。 @@ -18,13 +18,13 @@ title: 通过 RPM 包手动部署 ## 第 1 步：准备节点服务器 -参照[物理机部署前准备工作](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md)的内容，完成节点服务器的准备工作。 +参照[部署前准备工作](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md)的内容，完成节点服务器的准备工作。 ## 第 2 步：安装 RPM 包 -在完成准备工作后，就可以安装 Cloudberry Database 了。你需要从 [Cloudberry Database 发布页面](https://github.com/cloudberrydb/cloudberrydb/releases)下载对应的 RPM 安装包，然后在每个节点上通过安装包进行安装。 +在完成准备工作后，就可以安装 Apache Cloudberry 了。你需要从 [Apache Cloudberry 发布页面](https://github.com/cloudberrydb/cloudberrydb/releases)下载对应的 RPM 安装包，然后在每个节点上通过安装包进行安装。 -1. 下载 Cloudberry Database 的 RPM 安装包至 `gpadmin` 主目录 `/home/gpadmin/`： +1. 下载 Apache Cloudberry 的 RPM 安装包至 `gpadmin` 主目录 `/home/gpadmin/`： ```bash wget -P /home/gpadmin <下载地址> @@ -128,7 +128,7 @@ title: 通过 RPM 包手动部署 若无法执行 `gpssh`，可在 Coordinator 节点先执行如下命令 `source /usr/local/cloudberry-db/greenplum_path.sh`。 -## 第 4 步：初始化 Cloudberry Database +## 第 4 步：初始化 Apache Cloudberry 执行以下操作前，你需要先执行 `su - gpadmin` 切换到 `gpadmin` 用户。 @@ -259,7 +259,7 @@ title: 通过 RPM 包手动部署 DATABASE_NAME=warehouse ``` -9. 初始化 Cloudberry Database。使用 `gpinitsystem` 命令进行初始化，命令示例如下： +9. 初始化 Apache Cloudberry。使用 `gpinitsystem` 命令进行初始化，命令示例如下： ```bash gpinitsystem -c gpinitsystem_config -h /home/gpadmin/seg_hosts @@ -275,7 +275,7 @@ title: 通过 RPM 包手动部署 ## 第 5 步：登录数据库 -至此，Cloudberry Database 已经成功部署，你可以参考以下命令来登录数据库： +至此，Apache Cloudberry 已经成功部署，你可以参考以下命令来登录数据库： ```bash psql -h -p -U -d @@ -283,12 +283,12 @@ psql -h -p -U -d 以上命令中： -- `` 是 Cloudberry Database 服务器的 Coordinator 节点 IP 地址。 -- `` 是 Cloudberry Database 的端口号，默认为 `5432`。 +- `` 是 Apache Cloudberry 服务器的 Coordinator 节点 IP 地址。 +- `` 是 Apache Cloudberry 的端口号，默认为 `5432`。 - `` 是数据库的用户名。 - `` 是要连接的数据库名称。 -执行命令后，系统将提示你输入数据库密码。输入正确的密码后，你将成功登录到 Cloudberry Database，并可以执行相应的 SQL 查询和操作。请确保你有正确的权限来访问目标数据库。 +执行命令后，系统将提示你输入数据库密码。输入正确的密码后，你将成功登录到 Apache Cloudberry，并可以执行相应的 SQL 查询和操作。请确保你有正确的权限来访问目标数据库。 ```sql [gpadmin@cddb-coordinator ~]$ psql warehouse diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md index 400fc3f7760..e900e5bbccf 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md @@ -2,9 +2,9 @@ title: 部署前准备 --- -# 物理机部署前准备工作 +# 物理机/虚拟机部署前准备工作 -在物理机上部署 Cloudberry Database 前，你需要做一些准备工作。在开始部署之前，请阅读本文档以及[软硬件配置要求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)。 +在物理机/虚拟机上部署 Cloudberry Database 前，你需要做一些准备工作。在开始部署之前，请阅读本文档以及[软硬件配置要求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)。 ## 规划部署架构 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md index 866fbb3f871..8962dc707dd 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md @@ -4,13 +4,13 @@ title: 软硬件配置需求 # 软硬件配置需求 -本文介绍 Cloudberry Database 所需要的软件和硬件配置需求。 +本文介绍 Apache Cloudberry 所需要的软件和硬件配置需求。 ## 硬件需求 -### 物理机 +### 支持的部署环境 -以下介绍 Cloudberry Database 在测试和生产环境中，推荐的物理机配置。 +Apache Cloudberry 支持在物理机和虚拟机上部署。以下是推荐的的环境配置。 #### 开发及测试环境 @@ -30,6 +30,8 @@ title: 软硬件配置需求 | ETCD | 16 核+ | 64 GB+ | SSD | 万兆网卡（2 块最佳） | 3+ | | FTS | 4 核+ | 8+ GB | SSD | 万兆网卡（2 块最佳） | 3+ | +Apache Cloudberry 还可以部署在公有云平台上，例如 AWS、Azure 和 GCP。基于这些平台上选择的实例类型，云端部署的硬件要求可能会有所不同。请参考具体云服务提供商的文档，了解符合或超出推荐硬件规格的实例配置。 + ### 存储 - 为了避免数据盘在高负载的情况下，影响操作系统正常的 I/O 响应，操作系统应当与数据盘挂载到不同的磁盘上。 @@ -96,7 +98,7 @@ mount /dev/data/data2 /data2/ ### 支持的操作系统 -CloudBerry Database 支持操作系统包括： +Apache Cloudberry 支持操作系统包括： - Kylin V10 SP1 或 SP2 - 中标麒麟 V7update6 diff --git a/sidebars.ts b/sidebars.ts index 9e8160d27f3..9f7f891f55b 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -30,7 +30,7 @@ const sidebars: SidebarsConfig = { }, { type: 'category', - label: 'Deploy on Physical Machine', + label: 'Deploy on Physical or Virtual Machine', items: ['cbdb-op-software-hardware', 'cbdb-op-prepare-to-deploy', 'cbdb-op-deploy-guide','deploy-cbdb-with-single-node'] } ] From e03f5d55699155f31bd1feae489c1dcdb8902094 Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Tue, 14 Jan 2025 14:08:25 +0800 Subject: [PATCH 2/2] replace cbdb with apache cloudberry --- docs/cbdb-op-deploy-guide.md | 28 +++++++++---------- docs/cbdb-op-prepare-to-deploy.md | 18 ++++++------ .../current.json | 2 +- .../current/cbdb-op-deploy-guide.md | 4 +-- .../current/cbdb-op-prepare-to-deploy.md | 22 +++++++-------- 5 files changed, 37 insertions(+), 37 deletions(-) diff --git a/docs/cbdb-op-deploy-guide.md b/docs/cbdb-op-deploy-guide.md index bb0dab32e60..998ba4577f1 100644 --- a/docs/cbdb-op-deploy-guide.md +++ b/docs/cbdb-op-deploy-guide.md @@ -2,27 +2,27 @@ title: Deploy Manually Using RPM Package --- -# Deploy Cloudberry Database Manually Using RPM Package +# Deploy Apache Cloudberry Manually Using RPM Package -This document introduces how to manually deploy Cloudberry Database on physical/virtual machines using RPM package. Before reading this document, it is recommended to first read the [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) and [Prepare to Deploy Cloudberry Database](/docs/cbdb-op-prepare-to-deploy.md). +This document introduces how to manually deploy Apache Cloudberry on physical/virtual machines using RPM package. Before reading this document, it is recommended to first read the [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) and [Prepare to Deploy Apache Cloudberry](/docs/cbdb-op-prepare-to-deploy.md). The deployment method in this document is for production environments. -The example in this document uses CentOS 7.6 and deploys Cloudberry Database v1.0.0. The main steps are as follows: +The example in this document uses CentOS 7.6 and deploys Apache Cloudberry v1.0.0. The main steps are as follows: 1. [Prepare node servers](#step-1-prepare-server-nodes). 2. [Install the RPM package](#step-2-install-the-rpm-package). 3. [Configure mutual trust between nodes](#step-3-configure-mutual-trust-between-nodes). -4. [Initialize the database](#step-4-initialize-cloudberry-database). -5. [Log into the database](#step-5-log-into-cloudberry-database). +4. [Initialize the database](#step-4-initialize-apache-cloudberry). +5. [Log into the database](#step-5-log-into-apache-cloudberry). ## Step 1: Prepare server nodes -Read the [Prepare to Deploy Cloudberry Database](/docs/cbdb-op-prepare-to-deploy.md) document to prepare the server nodes. +Read the [Prepare to Deploy Apache Cloudberry](/docs/cbdb-op-prepare-to-deploy.md) document to prepare the server nodes. ## Step 2. Install the RPM package -After the preparation, it is time to install Cloudberry Database. You need to download the corresponding RPM package from [Cloudberry Database Releases](https://github.com/cloudberrydb/cloudberrydb/releases), and then install the database on each node using the installation package. +After the preparation, it is time to install Apache Cloudberry. You need to download the corresponding RPM package from [Apache Cloudberry Releases](https://github.com/apache/cloudberry/releases), and then install the database on each node using the installation package. 1. Download the RPM package to the home directory of `gpadmin`. @@ -123,7 +123,7 @@ After the preparation, it is time to install Cloudberry Database. You need to do If you fail to run `gpssh`, you can first run `source /usr/local/cloudberry-db/greenplum_path.sh` on the coordinator node. -## Step 4. Initialize Cloudberry Database +## Step 4. Initialize Apache Cloudberry Before performing the following operations, run `su - gpadmin` to switch to the `gpadmin` user. @@ -254,7 +254,7 @@ Before performing the following operations, run `su - gpadmin` to switch to the DATABASE_NAME=warehouse ``` -9. Use `gpinitsystem` to initialize Cloudberry Database. For example: +9. Use `gpinitsystem` to initialize Apache Cloudberry. For example: ```bash gpinitsystem -c gpinitsystem_config -h /home/gpadmin/seg_hosts @@ -268,9 +268,9 @@ Before performing the following operations, run `su - gpadmin` to switch to the gpinitstandby -s cbdb-standbycoordinator ``` -## Step 5. Log into Cloudberry Database +## Step 5. Log into Apache Cloudberry -Now you have successfully deployed Cloudberry Database. To log into the database, refer to the following command: +Now you have successfully deployed Apache Cloudberry. To log into the database, refer to the following command: ```bash psql -h -p -U -d @@ -278,12 +278,12 @@ psql -h -p -U -d In the command above: -- `` is the IP address of the coordinator node of the Cloudberry Database server. -- `` is the default port number of Cloudberry Database, which is `5432` by default. +- `` is the IP address of the coordinator node of the Apache Cloudberry server. +- `` is the default port number of Apache Cloudberry, which is `5432` by default. - `` is the user name of the database. - `` is the name of the database to connect. -After you run the `psql` command, the system will prompt you to enter the database password. After you enter the correct password, you will successfully log into the Cloudberry Database and can perform SQL queries and operations. Make sure that you have the correct permissions to access the target database. +After you run the `psql` command, the system will prompt you to enter the database password. After you enter the correct password, you will successfully log into Apache Cloudberry and can perform SQL queries and operations. Make sure that you have the correct permissions to access the target database. ```sql [gpadmin@cddb-coordinator ~]$ psql warehouse diff --git a/docs/cbdb-op-prepare-to-deploy.md b/docs/cbdb-op-prepare-to-deploy.md index 17c18223101..58fa2dc9c3d 100644 --- a/docs/cbdb-op-prepare-to-deploy.md +++ b/docs/cbdb-op-prepare-to-deploy.md @@ -4,11 +4,11 @@ title: Prepare to Deploy # Prepare to Deploy on Physical or Virtual Machine -Before deploying Cloudberry Database on physical or virtual machines, you need to do some preparations. Read this document and [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) before you start to deploy Cloudberry Database. +Before deploying Apache Cloudberry on physical or virtual machines, you need to do some preparations. Read this document and [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md) before you start to deploy Apache Cloudberry. ## Plan the deployment architecture -Plan your deployment architecture based on the [Cloudberry Database Architecture](/docs/cbdb-architecture.md) and [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md), and determine the number of servers needed. Ensure that all servers are within a single security group and have mutual trust configured. +Plan your deployment architecture based on the [Apache Cloudberry Architecture](/docs/cbdb-architecture.md) and [Software and Hardware Configuration Requirements](/docs/cbdb-op-software-hardware.md), and determine the number of servers needed. Ensure that all servers are within a single security group and have mutual trust configured. The deployment plan for the example of this document includes 1 coordinator + 1 standby + 3 segments (primary + mirror), totaling 5 servers. @@ -163,9 +163,9 @@ In the `/etc/sysctl.conf` configuration file, #### Port -In the `/etc/sysctl.conf` configuration file, `net.ipv4.ip_local_port_range` is used to specify the port range. To avoid port conflicts between Cloudberry Database and other applications, you need to specify the port range via operating system parameters. When you later set Cloudberry Database initialization parameters, avoid setting Cloudberry Database related ports in this range. +In the `/etc/sysctl.conf` configuration file, `net.ipv4.ip_local_port_range` is used to specify the port range. To avoid port conflicts between Apache Cloudberry and other applications, you need to specify the port range via operating system parameters. When you later set Apache Cloudberry initialization parameters, avoid setting Apache Cloudberry related ports in this range. -For example, for `net.ipv4.ip_local_port_range = 10000 65535`, you need to avoid setting the Cloudberry Database related ports in the interval `[10000,65535]`. You can set them to `6000` and `7000`: +For example, for `net.ipv4.ip_local_port_range = 10000 65535`, you need to avoid setting the Apache Cloudberry related ports in the interval `[10000,65535]`. You can set them to `6000` and `7000`: ``` PORT_BASE = 6000 @@ -174,7 +174,7 @@ MIRROR_PORT_BASE = 7000 #### IP segmentation -When the Cloudberry Database uses the UDP protocol for internal connection, the network card controls the fragmentation and reassembly of IP packets. If the size of a UDP message is larger than the maximum size of network transmission unit (MTU), the IP layer fragments the message. +When the Apache Cloudberry uses the UDP protocol for internal connection, the network card controls the fragmentation and reassembly of IP packets. If the size of a UDP message is larger than the maximum size of network transmission unit (MTU), the IP layer fragments the message. - `net.ipv4.ipfrag_high_thresh`: When the total size of IP fragments exceeds this threshold, the kernel will attempt to reorganize IP fragments. If the fragments exceed this threshold but all fragments have not arrived within the specified time, the kernel will not reorganize the fragments. This threshold is typically used to control whether larger shards are reorganized. The default value is `4194304` bytes (4 MB). - `net.ipv4.ipfrag_low_thresh`: Indicates that when the total size of IP fragments is below this threshold, the kernel will wait as long as possible for more fragments to arrive, to allow for larger reorganizations. This threshold is used to minimize unfinished reorganization operations and improve system performance. The default value is `3145728` bytes (3 MB). @@ -247,7 +247,7 @@ Edit the `/etc/security/limits.conf` file and add the following content, which l #### Set mount options for the XFS file system -XFS is the file system for the data directory of Cloudberry Database. XFS has the following mount options: +XFS is the file system for the data directory of Apache Cloudberry. XFS has the following mount options: ``` rw,nodev,noatime,inode64 @@ -297,7 +297,7 @@ sudo /sbin/blockdev --setra 16384 /dev/vdc #### I/O scheduling policy settings for disks -The disk type, operating system and scheduling policies of Cloudberry Database are as follows: +The disk type, operating system and scheduling policies of Apache Cloudberry are as follows: @@ -388,7 +388,7 @@ cat /sys/kernel/mm/*transparent_hugepage/enabled #### Disable IPC object deletion -Disable IPC object deletion by setting the value of `RemoveIPC` to `no`. You can set this parameter in the `/etc/systemd/logind.conf` file of Cloudberry Database. +Disable IPC object deletion by setting the value of `RemoveIPC` to `no`. You can set this parameter in the `/etc/systemd/logind.conf` file of Apache Cloudberry. ``` RemoveIPC=no @@ -422,7 +422,7 @@ service sshd restart #### Clock synchronization -Cloudberry Database requires the clock synchronization to be configured for all hosts, and the clock synchronization service should be started when the host starts. You can choose one of the following synchronization methods: +Apache Cloudberry requires the clock synchronization to be configured for all hosts, and the clock synchronization service should be started when the host starts. You can choose one of the following synchronization methods: - Use the coordinator node's time as the source, and other hosts synchronize the clock of the coordinator node host. - Synchronize clocks using an external clock source. diff --git a/i18n/zh/docusaurus-plugin-content-docs/current.json b/i18n/zh/docusaurus-plugin-content-docs/current.json index 44453edf538..fcad9e6076b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current.json +++ b/i18n/zh/docusaurus-plugin-content-docs/current.json @@ -17,7 +17,7 @@ }, "sidebar.docsbars.category.Build from Source Code": { "message": "从源码编译安装", - "description": "The label for category building CloudberryDB from source code in sidebar docs" + "description": "The label for category building Cloudberry from source code in sidebar docs" }, "sidebar.docsbars.category.References": { "message": "参考指南", diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md index 76b003c6812..a92cc0a10ab 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-deploy-guide.md @@ -13,7 +13,7 @@ title: 通过 RPM 包手动部署 1. [准备节点服务器](#第-1-步准备节点服务器)。 2. [安装 RPM 包](#第-2-步安装-rpm-包)。 3. [配置节点间互信](#第-3-步配置节点间互信)。 -4. [初始化数据库](#第-4-步初始化-cloudberry-database)。 +4. [初始化数据库](#第-4-步初始化-apache-cloudberry)。 5. [登录数据库](#第-5-步登录数据库)。 ## 第 1 步：准备节点服务器 @@ -22,7 +22,7 @@ title: 通过 RPM 包手动部署 ## 第 2 步：安装 RPM 包 -在完成准备工作后，就可以安装 Apache Cloudberry 了。你需要从 [Apache Cloudberry 发布页面](https://github.com/cloudberrydb/cloudberrydb/releases)下载对应的 RPM 安装包，然后在每个节点上通过安装包进行安装。 +在完成准备工作后，就可以安装 Apache Cloudberry 了。你需要从 [Apache Cloudberry 发布页面](https://github.com/apache/cloudberry/releases)下载对应的 RPM 安装包，然后在每个节点上通过安装包进行安装。 1. 下载 Apache Cloudberry 的 RPM 安装包至 `gpadmin` 主目录 `/home/gpadmin/`： diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md index e900e5bbccf..39adf19fcae 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-prepare-to-deploy.md @@ -4,11 +4,11 @@ title: 部署前准备 # 物理机/虚拟机部署前准备工作 -在物理机/虚拟机上部署 Cloudberry Database 前，你需要做一些准备工作。在开始部署之前，请阅读本文档以及[软硬件配置要求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)。 +在物理机/虚拟机上部署 Apache Cloudberry 前，你需要做一些准备工作。在开始部署之前，请阅读本文档以及[软硬件配置要求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)。 ## 规划部署架构 -根据 [Cloudberry Database 架构](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-architecture.md)和[软硬件配置要求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)规划部署架构，确定所需的服务器数量。确保所有的服务器都在一个安全组内，并且配置了互信。 +根据 [Apache Cloudberry 架构](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-architecture.md)和[软硬件配置要求](/i18n/zh/docusaurus-plugin-content-docs/current/cbdb-op-software-hardware.md)规划部署架构，确定所需的服务器数量。确保所有的服务器都在一个安全组内，并且配置了互信。 本文示例的部署规划为 1 Coordinator + 1 Standby + 3 Segment (Primary + Mirror)，共 5 台服务器。 @@ -61,7 +61,7 @@ systemctl disable firewalld.service ### 修改网络映射 -检查 `/etc/hosts` 文件，确保该文件包含 Cloudberry Database 所有主机别名与其网络 IP 地址的映射。示例如下： +检查 `/etc/hosts` 文件，确保该文件包含 Apache Cloudberry 所有主机别名与其网络 IP 地址的映射。示例如下： ``` 192.168.1.101 cbdb-coordinator @@ -163,9 +163,9 @@ $ echo $(expr $(getconf _PHYS_PAGES) / 2 \* $(getconf PAGE_SIZE)) #### 端口设置 -在 `/etc/sysctl.conf` 配置文件中，`net.ipv4.ip_local_port_range` 用于指定端口范围。为了避免 Cloudberry Database 与其他应用程序之间出现端口冲突，需要通过操作系统参数指定端口范围。在后续设置 Cloudberry Database 初始化参数时候，请勿使用这个范围的端口。 +在 `/etc/sysctl.conf` 配置文件中，`net.ipv4.ip_local_port_range` 用于指定端口范围。为了避免 Apache Cloudberry 与其他应用程序之间出现端口冲突，需要通过操作系统参数指定端口范围。在后续设置 Apache Cloudberry 初始化参数时候，请勿使用这个范围的端口。 -假设 `net.ipv4.ip_local_port_range = 10000 65535`，那么 Cloudberry Database 相关的端口应避免设置在区间 `[10000,65535]` 内，可以设置为 `6000` 和 `7000`，示例如下： +假设 `net.ipv4.ip_local_port_range = 10000 65535`，那么 Apache Cloudberry 相关的端口应避免设置在区间 `[10000,65535]` 内，可以设置为 `6000` 和 `7000`，示例如下： ``` PORT_BASE = 6000 @@ -174,7 +174,7 @@ MIRROR_PORT_BASE = 7000 #### IP 分段设置 -当 Cloudberry Database 内部连接使用 UDP 协议，网卡会控制 IP 数据包的分段和重组。如果 UDP 消息的大小大于网络最大传输单元 (MTU) 的大小，IP 层会对消息进行分段。 +当 Apache Cloudberry 内部连接使用 UDP 协议，网卡会控制 IP 数据包的分段和重组。如果 UDP 消息的大小大于网络最大传输单元 (MTU) 的大小，IP 层会对消息进行分段。 - `net.ipv4.ipfrag_high_thresh`：当 IP 分片的总大小超过该阈值时，内核将尝试对 IP 分片进行重组。如果分片超过了这个阈值，但全部片段在规定的时间内仍未到达，内核则不会重组这些分片。该阈值通常用于控制是否对较大的分片进行重组。默认值为 `4194304` 字节（即 4 MB）。 - `net.ipv4.ipfrag_low_thresh`：表示当 IP 分片的总大小低于该阈值时，内核将尽可能地等待更多分片到达，以便进行更大的重组。这个阈值的目的是尽量减少未完成的重组操作，以提高系统性能。默认值为 `3145728` 字节（3 MB）。 @@ -247,7 +247,7 @@ net.ipv4.ipfrag_time = 60 #### 为 XFS 文件系统设置挂载选项 -XFS 是 Cloudberry Database 数据目录的文件系统，XFS 使用以下选项进行挂载： +XFS 是 Apache Cloudberry 数据目录的文件系统，XFS 使用以下选项进行挂载： ``` rw,nodev,noatime,inode64 @@ -297,7 +297,7 @@ sudo /sbin/blockdev --setra 16384 /dev/vdc #### 磁盘的 I/O 调度策略设置 -Cloudberry Database 的磁盘类型、操作系统以及调度策略如下： +Apache Cloudberry 的磁盘类型、操作系统以及调度策略如下：
@@ -374,7 +374,7 @@ grubby --info=ALL #### 禁用透明大页面 (THP) -你需要禁用透明大页面 (THP)，因为它会降低 Cloudberry Database 的性能。禁用的命令如下所： +你需要禁用透明大页面 (THP)，因为它会降低 Apache Cloudberry 的性能。禁用的命令如下所： ```bash grubby --update-kernel=ALL --args="transparent_hugepage=never" @@ -388,7 +388,7 @@ cat /sys/kernel/mm/*transparent_hugepage/enabled #### 禁用 IPC 对象删除 -禁用 IPC 对象删除，即把 `RemoveIPC` 的值设为 `no`。你可以在 Cloudberry Database 的 `/etc/systemd/logind.conf` 文件中设置该参数。 +禁用 IPC 对象删除，即把 `RemoveIPC` 的值设为 `no`。你可以在 Apache Cloudberry 的 `/etc/systemd/logind.conf` 文件中设置该参数。 ``` RemoveIPC=no @@ -422,7 +422,7 @@ service sshd restart #### 时钟同步设置 -Cloudberry Database 要求为所有主机配置时钟需要同步，时钟同步服务应当随主机启动而启动。有两种同步方式： +Apache Cloudberry 要求为所有主机配置时钟需要同步，时钟同步服务应当随主机启动而启动。有两种同步方式： - 使用 Coordinator 节点的时间作为来源，其他主机同步 Coordinator 节点主机的时钟。 - 使用外部时钟来源同步。