Skip to content
Permalink
Browse files

dev, v2.1, v3.0: fix broken links (#1335)

* dec, v2.1, v3.0: fix broken links

* v3.0: fix a link

* fix links
  • Loading branch information...
CaitinChen authored and lilin90 committed Jul 10, 2019
1 parent f9c73d3 commit e87e123135fddcf03ee47a3b68c2c2b8145e7bee
@@ -44,7 +44,7 @@ This is a list of TiDB adopters in various industries.
|[Hoodinn](https://www.crunchbase.com/organization/hoodinn)|Gaming||
|[Ping++](https://www.crunchbase.com/organization/ping-5)|Mobile Payment|[Chinese](https://pingcap.com/cases-cn/user-case-ping++/)|
|[Hainan eKing Technology](https://www.crunchbase.com/organization/hainan-eking-technology)|Enterprise Technology|[Chinese](https://pingcap.com/cases-cn/user-case-ekingtech/)|
|[LianLian Tech](http://www.10030.com.cn/web/)|Mobile Payment||
|[LianLian Tech](https://www.crunchbase.com/organization/lianlian-pay)|Mobile Payment||
|[Tongdun Technology](https://www.crunchbase.com/organization/tongdun-technology)|FinTech||
|[Wacai](https://www.crunchbase.com/organization/wacai)|FinTech||
|[Tree Finance](https://www.treefinance.com.cn/)|FinTech||
@@ -1015,7 +1015,7 @@ See [Key Metrics](/reference/key-monitoring-metrics/overview-dashboard.md).

#### Is there a better way of monitoring the key metrics?

The monitoring system of TiDB consists of Prometheus and Grafana. From the dashboard in Grafana, you can monitor various running metrics of TiDB which include the monitoring metrics of system resources, of client connection and SQL operation, of internal communication and Region scheduling. With these metrics, the database administrator can better understand the system running status, running bottlenecks and so on. In the practice of monitoring these metrics, we list the key metrics of each TiDB component. Generally you only need to pay attention to these common metrics. For details, see [Key Metrics](/reference/key-monitoring-metrics/overview.md).
The monitoring system of TiDB consists of Prometheus and Grafana. From the dashboard in Grafana, you can monitor various running metrics of TiDB which include the monitoring metrics of system resources, of client connection and SQL operation, of internal communication and Region scheduling. With these metrics, the database administrator can better understand the system running status, running bottlenecks and so on. In the practice of monitoring these metrics, we list the key metrics of each TiDB component. Generally you only need to pay attention to these common metrics. For details, see [Key Metrics](/reference/key-monitoring-metrics/overview-dashboard.md).

#### The Prometheus monitoring data is deleted every 15 days by default. Could I set it to two months or delete the monitoring data manually?

@@ -14,7 +14,7 @@ This document describes how to deploy a TiDB cluster in the [minikube](https://k

> **Note:**
>
> Although Minikube supports `--vm-driver=none` that uses host docker instead of VM, it is not fully tested with TiDB Operator and may not work. If you want to try TiDB Operator on a system without virtualization support (e.g., on a VPS), you might consider using [DinD](local-dind-tutorial.md) instead.
> Although Minikube supports `--vm-driver=none` that uses host docker instead of VM, it is not fully tested with TiDB Operator and may not work. If you want to try TiDB Operator on a system without virtualization support (e.g., on a VPS), you might consider using [DinD](/how-to/get-started/deploy-tidb-from-kubernetes-dind.md) instead.
### Install minikube and start a Kubernetes cluster

@@ -16,7 +16,7 @@ When you perform a rolling update for a TiDB cluster, the service is shut down s

- To upgrade between large versions, you must upgrade [`tidb-ansible`](https://github.com/pingcap/tidb-ansible).

- To upgrade TiDB 2.0 (TiDB 2.0.1 or later) or TiDB 2.1 RC version to TiDB 2.1 GA version, see [TiDB 2.1 Upgrade Guide](/v2.1/how-to/upgrade/from-previous-version.md).
- To upgrade TiDB 2.0 (TiDB 2.0.1 or later) or TiDB 2.1 RC version to TiDB 2.1 GA version, see [TiDB 2.1 Upgrade Guide](https://pingcap.com/docs/v2.1/how-to/upgrade/from-previous-version/).
- To upgrade TiDB 2.0 (TiDB 2.0.1 or later) or TiDB 2.1 RC to TiDB 3.0, see [TiDB 3.0 Upgrade Guide](/how-to/upgrade/from-previous-version.md).

- For a minor upgrade, it is also recommended to update `tidb-ansible` for the latest configuration file templates, features, and bug fixes.
@@ -39,7 +39,7 @@ This is a list of TiDB adopters in various industries.
|[Hoodinn](https://www.crunchbase.com/organization/hoodinn)|Gaming||
|[Ping++](https://www.crunchbase.com/organization/ping-5)|Mobile Payment|[Chinese](https://pingcap.com/cases-cn/user-case-ping++/)|
|[Hainan eKing Technology](https://www.crunchbase.com/organization/hainan-eking-technology)|Enterprise Technology|[Chinese](https://pingcap.com/cases-cn/user-case-ekingtech/)|
|[LianLian Tech](http://www.10030.com.cn/web/)|Mobile Payment||
|[LianLian Tech](https://www.crunchbase.com/organization/lianlian-pay)|Mobile Payment||
|[Tongdun Technology](https://www.crunchbase.com/organization/tongdun-technology)|FinTech||
|[Wacai](https://www.crunchbase.com/organization/wacai)|FinTech||
|[Tree Finance](https://www.treefinance.com.cn/)|FinTech||
@@ -42,7 +42,7 @@ This is a list of TiDB adopters in various industries.
|[Hoodinn](https://www.crunchbase.com/organization/hoodinn)|Gaming||
|[Ping++](https://www.crunchbase.com/organization/ping-5)|Mobile Payment|[Chinese](https://pingcap.com/cases-cn/user-case-ping++/)|
|[Hainan eKing Technology](https://www.crunchbase.com/organization/hainan-eking-technology)|Enterprise Technology|[Chinese](https://pingcap.com/cases-cn/user-case-ekingtech/)|
|[LianLian Tech](http://www.10030.com.cn/web/)|Mobile Payment||
|[LianLian Tech](https://www.crunchbase.com/organization/lianlian-pay)|Mobile Payment||
|[Tongdun Technology](https://www.crunchbase.com/organization/tongdun-technology)|FinTech||
|[Wacai](https://www.crunchbase.com/organization/wacai)|FinTech||
|[Tree Finance](https://www.treefinance.com.cn/)|FinTech||
@@ -44,7 +44,7 @@ This is a list of TiDB adopters in various industries.
|[Hoodinn](https://www.crunchbase.com/organization/hoodinn)|Gaming||
|[Ping++](https://www.crunchbase.com/organization/ping-5)|Mobile Payment|[Chinese](https://pingcap.com/cases-cn/user-case-ping++/)|
|[Hainan eKing Technology](https://www.crunchbase.com/organization/hainan-eking-technology)|Enterprise Technology|[Chinese](https://pingcap.com/cases-cn/user-case-ekingtech/)|
|[LianLian Tech](http://www.10030.com.cn/web/)|Mobile Payment||
|[LianLian Tech](https://www.crunchbase.com/organization/lianlian-pay)|Mobile Payment||
|[Tongdun Technology](https://www.crunchbase.com/organization/tongdun-technology)|FinTech||
|[Wacai](https://www.crunchbase.com/organization/wacai)|FinTech||
|[Tree Finance](https://www.treefinance.com.cn/)|FinTech||
@@ -1017,7 +1017,7 @@ See [Key Metrics](/reference/key-monitoring-metrics/overview-dashboard.md).

#### Is there a better way of monitoring the key metrics?

The monitoring system of TiDB consists of Prometheus and Grafana. From the dashboard in Grafana, you can monitor various running metrics of TiDB which include the monitoring metrics of system resources, of client connection and SQL operation, of internal communication and Region scheduling. With these metrics, the database administrator can better understand the system running status, running bottlenecks and so on. In the practice of monitoring these metrics, we list the key metrics of each TiDB component. Generally you only need to pay attention to these common metrics. For details, see [Key Metrics](/reference/key-monitoring-metrics/overview.md).
The monitoring system of TiDB consists of Prometheus and Grafana. From the dashboard in Grafana, you can monitor various running metrics of TiDB which include the monitoring metrics of system resources, of client connection and SQL operation, of internal communication and Region scheduling. With these metrics, the database administrator can better understand the system running status, running bottlenecks and so on. In the practice of monitoring these metrics, we list the key metrics of each TiDB component. Generally you only need to pay attention to these common metrics. For details, see [Key Metrics](/reference/key-monitoring-metrics/overview-dashboard.md).

#### The Prometheus monitoring data is deleted every 15 days by default. Could I set it to two months or delete the monitoring data manually?

@@ -45,7 +45,7 @@ This is a list of TiDB adopters in various industries.
|[Hoodinn](https://www.crunchbase.com/organization/hoodinn)|Gaming||
|[Ping++](https://www.crunchbase.com/organization/ping-5)|Mobile Payment|[Chinese](https://pingcap.com/cases-cn/user-case-ping++/)|
|[Hainan eKing Technology](https://www.crunchbase.com/organization/hainan-eking-technology)|Enterprise Technology|[Chinese](https://pingcap.com/cases-cn/user-case-ekingtech/)|
|[LianLian Tech](http://www.10030.com.cn/web/)|Mobile Payment||
|[LianLian Tech](https://www.crunchbase.com/organization/lianlian-pay)|Mobile Payment||
|[Tongdun Technology](https://www.crunchbase.com/organization/tongdun-technology)|FinTech||
|[Wacai](https://www.crunchbase.com/organization/wacai)|FinTech||
|[Tree Finance](https://www.treefinance.com.cn/)|FinTech||
@@ -1016,7 +1016,7 @@ See [Key Metrics](/reference/key-monitoring-metrics/overview-dashboard.md).

#### Is there a better way of monitoring the key metrics?

The monitoring system of TiDB consists of Prometheus and Grafana. From the dashboard in Grafana, you can monitor various running metrics of TiDB which include the monitoring metrics of system resources, of client connection and SQL operation, of internal communication and Region scheduling. With these metrics, the database administrator can better understand the system running status, running bottlenecks and so on. In the practice of monitoring these metrics, we list the key metrics of each TiDB component. Generally you only need to pay attention to these common metrics. For details, see [Key Metrics](/reference/key-monitoring-metrics/overview.md).
The monitoring system of TiDB consists of Prometheus and Grafana. From the dashboard in Grafana, you can monitor various running metrics of TiDB which include the monitoring metrics of system resources, of client connection and SQL operation, of internal communication and Region scheduling. With these metrics, the database administrator can better understand the system running status, running bottlenecks and so on. In the practice of monitoring these metrics, we list the key metrics of each TiDB component. Generally you only need to pay attention to these common metrics. For details, see [Key Metrics](/reference/key-monitoring-metrics/overview-dashboard.md).

#### The Prometheus monitoring data is deleted every 15 days by default. Could I set it to two months or delete the monitoring data manually?

@@ -14,7 +14,7 @@ This document describes how to deploy a TiDB cluster in the [minikube](https://k

> **Note:**
>
> Although Minikube supports `--vm-driver=none` that uses host docker instead of VM, it is not fully tested with TiDB Operator and may not work. If you want to try TiDB Operator on a system without virtualization support (e.g., on a VPS), you might consider using [DinD](local-dind-tutorial.md) instead.
> Although Minikube supports `--vm-driver=none` that uses host docker instead of VM, it is not fully tested with TiDB Operator and may not work. If you want to try TiDB Operator on a system without virtualization support (e.g., on a VPS), you might consider using [DinD](/how-to/get-started/deploy-tidb-from-kubernetes-dind.md) instead.
### Install minikube and start a Kubernetes cluster

@@ -17,7 +17,7 @@ When you perform a rolling update for a TiDB cluster, the service is shut down s

- To upgrade between large versions, you must upgrade [`tidb-ansible`](https://github.com/pingcap/tidb-ansible).

- To upgrade TiDB 2.0 (TiDB 2.0.1 or later) or TiDB 2.1 RC version to TiDB 2.1 GA version, see [TiDB 2.1 Upgrade Guide](/v2.1/how-to/upgrade/from-previous-version.md).
- To upgrade TiDB 2.0 (TiDB 2.0.1 or later) or TiDB 2.1 RC version to TiDB 2.1 GA version, see [TiDB 2.1 Upgrade Guide](https://pingcap.com/docs/v2.1/how-to/upgrade/from-previous-version/).
- To upgrade TiDB 2.0 (TiDB 2.0.1 or later) or TiDB 2.1 RC to TiDB 3.0, see [TiDB 3.0 Upgrade Guide](/how-to/upgrade/from-previous-version.md).

- For a minor upgrade, it is also recommended to update `tidb-ansible` for the latest configuration file templates, features, and bug fixes.
@@ -37,7 +37,7 @@ update mysql.tidb set VARIABLE_VALUE="30m" where VARIABLE_NAME="tikv_gc_run_inte

> **Note:**
>
> - The value of `tikv_gc_life_time` must be greater than that of [`max-txn-time-use`](/reference/configuration/tidb-server/configuration-file#max-txn-time-use) in the TiDB configuration file by at least 10 seconds, and must than or equal to 10 minutes.
> - The value of `tikv_gc_life_time` must be greater than that of [`max-txn-time-use`](/reference/configuration/tidb-server/configuration-file.md#max-txn-time-use) in the TiDB configuration file by at least 10 seconds, and must than or equal to 10 minutes.
> - In scenarios of frequent updates, a large value (days or even months) for `tikv_gc_life_time` may cause potential issues, such as:
> - Larger storage use
> - A large amount of history data may affect performance to a certain degree, especially for range queries such as `select count(*) from t`
@@ -34,7 +34,7 @@ DM-worker executes specific data replication tasks.
- Orchestrating the operation of the data replication subtasks
- Monitoring the running state of the data replication subtasks

After DM-worker is started, it automatically replicates the upstream binlog to the local configuration directory (the default replication directory is `<deploy_dir>/relay_log` if DM is deployed using `DM-Ansible`). For details about DM-worker, see [DM-worker Introduction](/reference/tools/data-migration/dm-worker-intro.md). For details about the relay log, see [Relay Log](/tools/dm/relay-log.md).
After DM-worker is started, it automatically replicates the upstream binlog to the local configuration directory (the default replication directory is `<deploy_dir>/relay_log` if DM is deployed using `DM-Ansible`). For details about DM-worker, see [DM-worker Introduction](/reference/tools/data-migration/dm-worker-intro.md). For details about the relay log, see [Relay Log](/reference/tools/data-migration/relay-log.md).

### dmctl

0 comments on commit e87e123

Please sign in to comment.
You can’t perform that action at this time.