Skip to content
Permalink
Browse files

dev, v3.0, v2.1: update links according to the new link format (#1501)

* dev, v3.0, v2.1: update links according to the new link format

* v3.0: change all link format

* v2.1: update all link format

* update two more links

* fix one link

* update check script

* fix remaining lint issues
  • Loading branch information...
yikeke authored and YiniXu9506 committed Sep 4, 2019
1 parent 554cb46 commit e8f970f2801d19c63873aded68019afbda906523
Showing 530 changed files with 3,140 additions and 3,125 deletions.

Large diffs are not rendered by default.

@@ -10,25 +10,25 @@ TiDB ("Ti" stands for Titanium) is an open-source NewSQL database that supports

TiDB can be deployed on-premise or in-cloud. The following deployment options are officially supported by PingCAP:

- [Ansible Deployment](/how-to/deploy/orchestrated/ansible.md): This guide describes how to deploy TiDB using Ansible. It is strongly recommended for production deployment.
- [Ansible Offline Deployment](/how-to/deploy/orchestrated/offline-ansible.md): If your environment has no access to the internet, you can follow this guide to see how to deploy a TiDB cluster offline using Ansible.
- [Docker Deployment](/how-to/deploy/orchestrated/docker.md): This guide describes how to deploy TiDB using Docker.
- [Docker Compose Deployment](/how-to/get-started/deploy-tidb-from-docker-compose.md): This guide describes how to deploy TiDB using Docker compose. You can follow this guide to quickly deploy a TiDB cluster for testing and development on your local drive.
- [Ansible Deployment](/dev/how-to/deploy/orchestrated/ansible.md): This guide describes how to deploy TiDB using Ansible. It is strongly recommended for production deployment.
- [Ansible Offline Deployment](/dev/how-to/deploy/orchestrated/offline-ansible.md): If your environment has no access to the internet, you can follow this guide to see how to deploy a TiDB cluster offline using Ansible.
- [Docker Deployment](/dev/how-to/deploy/orchestrated/docker.md): This guide describes how to deploy TiDB using Docker.
- [Docker Compose Deployment](/dev/how-to/get-started/deploy-tidb-from-docker-compose.md): This guide describes how to deploy TiDB using Docker compose. You can follow this guide to quickly deploy a TiDB cluster for testing and development on your local drive.
- Kubernetes Deployment:

You can use [TiDB Operator](https://github.com/pingcap/tidb-operator) to deploy TiDB on:

- [AWS EKS (Elastic Kubernetes Service)](/tidb-in-kubernetes/deploy/aws-eks.md)
- [GKE (Google Kubernetes Engine)](/tidb-in-kubernetes/deploy/gcp-gke.md)
- [Google Cloud Shell](/tidb-in-kubernetes/get-started/deploy-tidb-from-kubernetes-gke.md)
- [Alibaba Cloud ACK (Container Service for Kubernetes)](/tidb-in-kubernetes/deploy/alibaba-cloud.md)
- [AWS EKS (Elastic Kubernetes Service)](/dev/tidb-in-kubernetes/deploy/aws-eks.md)
- [GKE (Google Kubernetes Engine)](/dev/tidb-in-kubernetes/deploy/gcp-gke.md)
- [Google Cloud Shell](/dev/tidb-in-kubernetes/get-started/deploy-tidb-from-kubernetes-gke.md)
- [Alibaba Cloud ACK (Container Service for Kubernetes)](/dev/tidb-in-kubernetes/deploy/alibaba-cloud.md)

Or deploy TiDB locally using:

- [DinD (Docker in Docker)](/tidb-in-kubernetes/get-started/deploy-tidb-from-kubernetes-dind.md)
- [Minikube](/tidb-in-kubernetes/get-started/deploy-tidb-from-kubernetes-minikube.md)
- [DinD (Docker in Docker)](/dev/tidb-in-kubernetes/get-started/deploy-tidb-from-kubernetes-dind.md)
- [Minikube](/dev/tidb-in-kubernetes/get-started/deploy-tidb-from-kubernetes-minikube.md)

- [Binary Tarball Deployment](/how-to/deploy/from-tarball/production-environment.md): This guide describes how to deploy TiDB from a binary tarball in production. Guides for [development](/how-to/get-started/deploy-tidb-from-binary.md) and [testing](/how-to/deploy/from-tarball/testing-environment.md) environments are also available.
- [Binary Tarball Deployment](/dev/how-to/deploy/from-tarball/production-environment.md): This guide describes how to deploy TiDB from a binary tarball in production. Guides for [development](/dev/how-to/get-started/deploy-tidb-from-binary.md) and [testing](/dev/how-to/deploy/from-tarball/testing-environment.md) environments are also available.

## Community Provided Blog Posts & Tutorials

@@ -6,7 +6,7 @@ category: introduction

# TiDB Architecture

The TiDB platform is comprised of three key components: the TiDB server, the PD server, and the TiKV server. In addition, TiDB also provides the [TiSpark](https://github.com/pingcap/tispark/) component for complex OLAP requirements and the [TiDB Operator](/tidb-in-kubernetes/tidb-operator-overview.md) to make things simpler for the deployment and management on cloud.
The TiDB platform is comprised of three key components: the TiDB server, the PD server, and the TiKV server. In addition, TiDB also provides the [TiSpark](https://github.com/pingcap/tispark/) component for complex OLAP requirements and the [TiDB Operator](/dev/tidb-in-kubernetes/tidb-operator-overview.md) to make things simpler for the deployment and management on cloud.

![image alt text](/media/tidb-architecture.png)

@@ -9,9 +9,9 @@ In this test, Sysbench 1.0.14 and TiDB 3.0 Beta are used. It is recommended to u

## Test environment

- [Hardware recommendations](/how-to/deploy/hardware-recommendations.md)
- [Hardware recommendations](/dev/how-to/deploy/hardware-recommendations.md)

- The TiDB cluster is deployed according to the [TiDB Deployment Guide](/how-to/deploy/orchestrated/ansible.md). Suppose there are 3 servers in total. It is recommended to deploy 1 TiDB instance, 1 PD instance and 1 TiKV instance on each server. As for disk space, supposing that there are 32 tables and 10M rows of data on each table, it is recommended that the disk space where TiKV's data directory resides is larger than 512 GB.
- The TiDB cluster is deployed according to the [TiDB Deployment Guide](/dev/how-to/deploy/orchestrated/ansible.md). Suppose there are 3 servers in total. It is recommended to deploy 1 TiDB instance, 1 PD instance and 1 TiKV instance on each server. As for disk space, supposing that there are 32 tables and 10M rows of data on each table, it is recommended that the disk space where TiKV's data directory resides is larger than 512 GB.

The number of concurrent connections to a single TiDB cluster is recommended to be under 500. If you need to increase the concurrency pressure on the entire system, you can add TiDB instances to the cluster whose number depends on the pressure of the test.

@@ -87,7 +87,7 @@ sync-log = false
capacity = "30GB"
```

For more detailed information on TiKV performance tuning, see [Tune TiKV Performance](/reference/performance/tune-tikv.md).
For more detailed information on TiKV performance tuning, see [Tune TiKV Performance](/dev/reference/performance/tune-tikv.md).

## Test process

@@ -96,7 +96,7 @@ enabled = true

### Configure TiKV

You can use the basic configuration at the beginning. Then after the test is run, you can adjust it based on the metrics on Grafana and the [TiKV Tuning Instructions](../reference/performance/tune-tikv.md).
You can use the basic configuration at the beginning. Then after the test is run, you can adjust it based on the metrics on Grafana and the [TiKV Tuning Instructions](/dev/reference/performance/tune-tikv.md).

### Configure BenchmarkSQL

@@ -54,8 +54,8 @@ mysql> ADMIN CHECKSUM TABLE `schema`.`table`;
## What kind of data source format is supported by Lightning?

In version 2.1.6, TiDB Lightning only supports the SQL dump generated by
[Mydumper](/reference/tools/mydumper.md)
or [CSV files](/reference/tools/tidb-lightning/csv.md) stored in the local filesystem.
[Mydumper](/dev/reference/tools/mydumper.md)
or [CSV files](/dev/reference/tools/tidb-lightning/csv.md) stored in the local filesystem.

## Could TiDB Lightning skip creating schema and tables?

0 comments on commit e8f970f

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