diff --git a/deploy-monitoring-services.md b/deploy-monitoring-services.md index 95acc4d2424cd..3a36c791f21fc 100644 --- a/deploy-monitoring-services.md +++ b/deploy-monitoring-services.md @@ -26,9 +26,9 @@ Assume that the TiDB cluster topology is as follows: ```bash # Downloads the package. -wget https://download.pingcap.org/prometheus-2.27.1.linux-amd64.tar.gz -wget https://download.pingcap.org/node_exporter-v1.3.1-linux-amd64.tar.gz -wget https://download.pingcap.org/grafana-7.5.11.linux-amd64.tar.gz +wget https://download.pingcap.com/prometheus-2.27.1.linux-amd64.tar.gz +wget https://download.pingcap.com/node_exporter-v1.3.1-linux-amd64.tar.gz +wget https://download.pingcap.com/grafana-7.5.11.linux-amd64.tar.gz ``` {{< copyable "shell-regular" >}} diff --git a/dm/dm-faq.md b/dm/dm-faq.md index ca4ee4d42f135..ae3c9547c2a9b 100644 --- a/dm/dm-faq.md +++ b/dm/dm-faq.md @@ -242,7 +242,7 @@ This is a known bug of TiUP, which is fixed in TiUP v1.3.2. The following are tw 2. Scale in and then scale out Grafana nodes in the cluster to restart the Grafana service. - Solution two: 1. Back up the `deploy/grafana-$port/bin/public` folder. - 2. Download the [TiUP DM offline package](https://download.pingcap.org/tidb-dm-v2.0.1-linux-amd64.tar.gz) and unpack it. + 2. Download the [TiUP DM offline package](https://download.pingcap.com/tidb-dm-v2.0.1-linux-amd64.tar.gz) and unpack it. 3. Unpack the `grafana-v4.0.3-**.tar.gz` in the offline package. 4. Replace the folder `deploy/grafana-$port/bin/public` with the `public` folder in `grafana-v4.0.3-**.tar.gz`. 5. Execute `tiup dm restart $cluster_name -R grafana` to restart the Grafana service. diff --git a/dm/quick-start-create-task.md b/dm/quick-start-create-task.md index 1f455dff90d92..60359835baa15 100644 --- a/dm/quick-start-create-task.md +++ b/dm/quick-start-create-task.md @@ -73,7 +73,7 @@ To run a TiDB server, use the following command: {{< copyable "shell-regular" >}} ```bash -wget https://download.pingcap.org/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz +wget https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz tar -xzvf tidb-latest-linux-amd64.tar.gz mv tidb-latest-linux-amd64/bin/tidb-server ./ ./tidb-server diff --git a/download-ecosystem-tools.md b/download-ecosystem-tools.md index 50443f7d20bef..74b15fe2cfafd 100644 --- a/download-ecosystem-tools.md +++ b/download-ecosystem-tools.md @@ -24,14 +24,14 @@ TiDB Toolkit contains frequently used TiDB tools, such as data export tool Dumpl You can download TiDB Toolkit from the following link: ``` -https://download.pingcap.org/tidb-community-toolkit-{version}-linux-{arch}.tar.gz +https://download.pingcap.com/tidb-community-toolkit-{version}-linux-{arch}.tar.gz ``` -`{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v6.2.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v6.2.0-linux-amd64.tar.gz`. +`{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v6.2.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v6.2.0-linux-amd64.tar.gz`. > **Note:** > -> If you need to download the [PD Control](/pd-control.md) tool `pd-ctl`, download the TiDB installation package separately from `https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz`. +> If you need to download the [PD Control](/pd-control.md) tool `pd-ctl`, download the TiDB installation package separately from `https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz`. ## TiDB Toolkit description diff --git a/pd-control.md b/pd-control.md index cfb9dfeaeead4..741b34c09ca34 100644 --- a/pd-control.md +++ b/pd-control.md @@ -23,12 +23,12 @@ To obtain `pd-ctl` of the latest version, download the TiDB server installation | Installation package | OS | Architecture | SHA256 checksum | | :------------------------------------------------------------------------ | :------- | :---- | :--------------------------------------------------------------- | -| `https://download.pingcap.org/tidb-community-server-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.org/tidb-community-server-{version}-linux-amd64.tar.gz.sha256` | -| `https://download.pingcap.org/tidb-community-server-{version}-linux-arm64.tar.gz` (pd-ctl) | Linux | arm64 | `https://download.pingcap.org/tidb-community-server-{version}-linux-arm64.tar.gz.sha256` | +| `https://download.pingcap.com/tidb-community-server-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.com/tidb-community-server-{version}-linux-amd64.tar.gz.sha256` | +| `https://download.pingcap.com/tidb-community-server-{version}-linux-arm64.tar.gz` (pd-ctl) | Linux | arm64 | `https://download.pingcap.com/tidb-community-server-{version}-linux-arm64.tar.gz.sha256` | > **Note:** > -> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz`. +> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz`. ### Compile from source code diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md index 9abba0748a67a..b28ed819f0d79 100644 --- a/production-deployment-using-tiup.md +++ b/production-deployment-using-tiup.md @@ -89,16 +89,16 @@ Perform the following steps in this section to deploy a TiDB cluster offline usi **Method 1**: Download the offline binary packages (TiUP offline package included) of the target TiDB version using the following links. You need to download both the server and toolkit packages. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/). ``` -https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz +https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz ``` ``` -https://download.pingcap.org/tidb-community-toolkit-{version}-linux-{arch}.tar.gz +https://download.pingcap.com/tidb-community-toolkit-{version}-linux-{arch}.tar.gz ``` > **Tip:** > -> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.5.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.5.0-linux-amd64.tar.gz`. +> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v7.5.0-linux-amd64.tar.gz`. **Method 2**: Manually pack an offline component package using `tiup mirror clone`. The detailed steps are as follows: diff --git a/tidb-binlog/get-started-with-tidb-binlog.md b/tidb-binlog/get-started-with-tidb-binlog.md index abcb12958d7fb..c000e0cac8c8c 100644 --- a/tidb-binlog/get-started-with-tidb-binlog.md +++ b/tidb-binlog/get-started-with-tidb-binlog.md @@ -42,14 +42,14 @@ sudo yum install -y mariadb-server ``` ```bash -curl -L https://download.pingcap.org/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz | tar xzf - +curl -L https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz | tar xzf - cd tidb-latest-linux-amd64 ``` Expected output: ``` -[kolbe@localhost ~]$ curl -LO https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - +[kolbe@localhost ~]$ curl -LO https://download.pingcap.com/tidb-latest-linux-amd64.tar.gz | tar xzf - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 368M 100 368M 0 0 8394k 0 0:00:44 0:00:44 --:--:-- 11.1M diff --git a/upgrade-monitoring-services.md b/upgrade-monitoring-services.md index e1db79862a609..cb1bb95337c2a 100644 --- a/upgrade-monitoring-services.md +++ b/upgrade-monitoring-services.md @@ -31,12 +31,12 @@ Download a new installation package from the [Prometheus download page](https:// 1. Download the TiDB server package and extract it. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/). ``` - https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz + https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz ``` > **Tip:** > - > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`. + > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`. 2. In the extracted files, locate `prometheus-v{version}-linux-{arch}.tar.gz` and extract it. @@ -80,12 +80,12 @@ In the following upgrade steps, you need to download the Grafana installation pa 1. Download the TiDB server package and extract it. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/). ``` - https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz + https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz ``` > **Tip:** > - > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`. + > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`. 2. In the extracted files, locate `grafana-v{version}-linux-{arch}.tar.gz` and extract it.