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.

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

tiup cluster check: support port connectivity check #1329

Open
pcqz opened this issue Apr 26, 2021 · 1 comment
Open

tiup cluster check: support port connectivity check #1329

pcqz opened this issue Apr 26, 2021 · 1 comment
Labels
component/cluster Issues about the tiup-cluster component type/feature-request Categorizes issue as related to a new feature.

Comments

@pcqz
Copy link

pcqz commented Apr 26, 2021

Feature Request

Is your feature request related to a problem? Please describe:

The ports required by tidb cluster is prohibited default by firewall in the case of cross-region deployment. After tiup cluster deployment, tiup cluster display result is normal when all nodes status are up, but connection between cluster nodes may fail.

Describe the feature you'd like:
I'd like that tiup cluster check can not only check port occupancy, but also perform port connectivity check.

Why the featue is needed:
In order to achieve cross-cloud high availability, users may deploy cluster in the public network environment.

Describe alternatives you've considered:
Login to each node and use Telnet command to check port connectivity.

Teachability, Documentation, Adoption, Migration Strategy:

@pcqz pcqz added the type/feature-request Categorizes issue as related to a new feature. label Apr 26, 2021
@AstroProfundis AstroProfundis added the component/cluster Issues about the tiup-cluster component label Apr 26, 2021
@dveeden
Copy link
Contributor

dveeden commented Jan 22, 2025

Related: #1087

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/cluster Issues about the tiup-cluster component type/feature-request Categorizes issue as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants