Skip to content

Commit

Permalink
add indentation
Browse files Browse the repository at this point in the history
  • Loading branch information
TomShawn authored Aug 5, 2021
1 parent 253e9e0 commit 57ce0a3
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions tiup/tiup-component-cluster-import.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@ Before TiDB v4.0, TiDB clusters were mainly deployed using TiDB Ansible. For TiD
>
> + After importing the TiDB Ansible configuration to TiUP for management, **DO NOT** use TiDB Ansible for cluster operations anymore. Otherwise, conflicts might be caused due to inconsistent meta information.
> + If the clusters deployed using TiDB Ansible are in any of the following situations, do not use the `import` command.
> + Clusters with TLS encryption enabled
> + Pure KV clusters (clusters without TiDB instances)
> + Clusters with Kafka enabled
> + Clusters with Spark enabled
> + Clusters with TiDB Lightning/TiKV Importer enabled
> + Clusters still using the old `push` mode to collect monitoring metrics (if you keep the default mode `pull` unchanged, using the `import` command is supported)
> + Clusters in which the non-default ports (the ports configured in the `group_vars` directory are compatible) are separately configured in the `inventory.ini` configuration file using `node_exporter_port` / `blackbox_exporter_port`
> + Clusters with TLS encryption enabled
> + Pure KV clusters (clusters without TiDB instances)
> + Clusters with Kafka enabled
> + Clusters with Spark enabled
> + Clusters with TiDB Lightning/TiKV Importer enabled
> + Clusters still using the old `push` mode to collect monitoring metrics (if you keep the default mode `pull` unchanged, using the `import` command is supported)
> + Clusters in which the non-default ports (the ports configured in the `group_vars` directory are compatible) are separately configured in the `inventory.ini` configuration file using `node_exporter_port` / `blackbox_exporter_port`
> + If some nodes in the cluster deployed with TiDB Ansible are not deployed with monitoring components, you should first use TiDB Ansible to add the corresponding node information in `monitored_servers`section of `inventory.ini` file, and then use `deploy.yaml` playbook to fully deployed monitoring components. Otherwise, after data is imported into TiUP, when you perform other maintenance operations, errors might occur due to the lack of monitoring components.
## Syntax
Expand Down

0 comments on commit 57ce0a3

Please sign in to comment.