Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tiup: add notice about importing cluster #6108

Merged
merged 4 commits into from
Aug 27, 2021
Merged

tiup: add notice about importing cluster #6108

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
253e9e0
tiup: add notice about importing cluster
Aug 5, 2021
57ce0a3
add indentation
TomShawn Aug 5, 2021
ce3aa67
Apply suggestions from code review
Liuxiaozhen12 Aug 5, 2021
217c714
Update tiup/tiup-component-cluster-import.md
Liuxiaozhen12 Aug 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions tiup/tiup-component-cluster-import.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,14 @@ 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.
Liuxiaozhen12 marked this conversation as resolved.
Show resolved Hide resolved

## Syntax

Expand Down