Skip to content
Permalink
Browse files

op-guide: add precaution when upgrading (#863)

* op-guide: add precaution when upgrading

Via: pingcap/docs-cn#1033

* op-guide: address the comment
  • Loading branch information...
yikeke authored and lilin90 committed Jan 18, 2019
1 parent c8fdb07 commit 51fd46a85f48c43da42131f52ce37bdd9bc81cf5
Showing with 8 additions and 0 deletions.
  1. +4 −0 op-guide/tidb-v2.0-upgrade-guide.md
  2. +4 −0 op-guide/tidb-v2.1-upgrade-guide.md
@@ -8,6 +8,10 @@ category: deployment

This document describes how to upgrade from TiDB 1.0 or TiDB 2.0 RC version to TiDB 2.0 GA version.

## Precaution

Do not execute any DDL statements during the upgrading process, otherwise the undefined behavior error might occur.

## Step 1: Install Ansible and dependencies in the Control Machine

TiDB-Ansible release-2.0 depends on Ansible 2.4.2 or later, and is compatible with the latest Ansible 2.5. In addition, TiDB-Ansible release-2.0 depends on the Python module: `jinja2>=2.9.6` and `jmespath>=0.9.0`.
@@ -20,6 +20,10 @@ For details about using Ansible to perform a rolling update to each component, s
- Roll update to 2.0.1 or later 2.0.x versions, and then roll update to the 2.1 version
- If you upgrade from TiDB 2.0.6 or earlier to TiDB 2.1, check if there is any ongoing DDL operation, especially the time consuming `Add Index` operation, because the DDL operations slow down the upgrading process. If there is ongoing DDL operation, wait for the DDL operation finishes and then roll update.

## Precaution

Do not execute any DDL statements during the upgrading process, otherwise the undefined behavior error might occur.

## Step 1: Install Ansible and dependencies on the Control Machine

TiDB-Ansible release-2.1 depends on Ansible 2.4.2 ~ 2.7.0 (`ansible>=2.4.2,<2.7.0`) and the Python module `jinja2>=2.9.6` and `jmespath>=0.9.0`.

0 comments on commit 51fd46a

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