`tiup cluster check`: support port connectivity check
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
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:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the tiup cluster check command and its existing port-occupancy check. Trace how cluster nodes and required ports are obtained, then define the connectivity result separately from occupancy; the work is done when cross-node blocked connectivity is reported by the command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100