mirror of https://github.com/tikv/website.git
Update wording after peer review
Signed-off-by: shichun-0415 <lishichun@pingcap.com>
This commit is contained in:
parent
aaf48d9a2b
commit
fe4740adfd
|
|
@ -148,7 +148,7 @@ For example, execute the following command to check the status of the `tikv-test
|
|||
tiup cluster display tikv-test
|
||||
```
|
||||
|
||||
The command output should include the instance ID, role, host, listening port, and status (the status of the cluster is `Down`/`inactive` because it is not started yet), and directory information.
|
||||
The command output includes the instance ID, role, host, listening port, and status (the status of the cluster is `Down`/`inactive` because it is not started yet), and directory information.
|
||||
|
||||
## Step 6: Start the TiKV cluster
|
||||
|
||||
|
|
|
|||
|
|
@ -206,7 +206,7 @@ To deploy a TiKV cluster with multiple nodes for test, take the following steps:
|
|||
--log-file=tikv3.log
|
||||
```
|
||||
|
||||
Use the [pd-ctl](https://github.com/pingcap/pd/tree/master/tools/pd-ctl) tool to verify whether PD and TiKV are successfully deployed:
|
||||
You can use the [pd-ctl](https://github.com/pingcap/pd/tree/master/tools/pd-ctl) tool to verify whether PD and TiKV are successfully deployed:
|
||||
|
||||
```
|
||||
./pd-ctl store -d -u http://192.168.199.113:2379
|
||||
|
|
|
|||
|
|
@ -17,14 +17,14 @@ This section introduces the preparation works needed before upgrading your TiKV
|
|||
|
||||
Before upgrading your TiKV cluster, you first need to upgrade TiUP.
|
||||
|
||||
1. Upgrade the TiUP version. It is recommended that the TiUP version be `1.4.0` or later.
|
||||
1. Upgrade the TiUP version to `1.4.0` or later.
|
||||
|
||||
```bash
|
||||
tiup update --self
|
||||
tiup --version
|
||||
```
|
||||
|
||||
2. Upgrade the TiUP Cluster version. It is recommended that the TiUP Cluster version be `1.4.0` or later.
|
||||
2. Upgrade the TiUP Cluster version to `1.4.0` or later.
|
||||
|
||||
```bash
|
||||
tiup update cluster
|
||||
|
|
@ -40,7 +40,7 @@ Skip this step if one of the following situations applies:
|
|||
+ After the upgrade, you want to use default parameter values of v5.0 for the unmodified configuration items.
|
||||
{{< /info >}}
|
||||
|
||||
1. Enter the `vi` editing mode to edit the topology file:
|
||||
1. Edit the topology file in `vi` editing mode:
|
||||
|
||||
```bash
|
||||
tiup cluster edit-config <cluster-name>
|
||||
|
|
@ -48,7 +48,7 @@ Skip this step if one of the following situations applies:
|
|||
|
||||
2. Refer to the format of [topology](https://github.com/pingcap/tiup/blob/release-1.4/embed/templates/examples/topology.example.yaml) configuration template and fill the parameters you want to modify in the `server_configs` section of the topology file.
|
||||
|
||||
3. After the modification, <kbd>:</kbd> + <kbd>w</kbd> + <kbd>q</kbd> to save the change and exit the editing mode. Enter <kbd>Y</kbd> to confirm the change.
|
||||
3. Save the changes and exit the editing mode.
|
||||
|
||||
## Perform a rolling upgrade to the TiKV cluster
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue