TiDB Software and Hardware Recommendations
Network Requirements
To run TiDB, an open source distributed NewSQL database, the following network port configuration is required. Based on the actual TiDB deployment environment, administrators can open the relevant ports on the network and host sides.
| Component | Default port | Description |
|---|---|---|
| TiDB | 4000 | Communication port for applications and DBA tools |
| TiDB | 10080 | Communication port for reporting TiDB status |
| TiKV | 20160 | TiKV communication port |
| TiKV | 20180 | Communication port for reporting TiKV status |
| PD | 2379 | Communication port between TiDB and PD |
| PD | 2380 | Communication port between nodes in the PD cluster |
| TiFlash | 9000 | TiFlash TCP service port |
| TiFlash | 8123 | TiFlash HTTP service port |
| TiFlash | 3930 | TiFlash RAFT and coprocessor service port |
| TiFlash | 20170 | TiFlash proxy service port |
| TiFlash | 20292 | Port where Prometheus pulls TiFlash Proxy metrics |
| TiFlash | 8234 | Port where Prometheus pulls TiFlash metrics |
| Pump | 8250 | Pump communication port |
| Drainer | 8249 | Drainer communication port |
| TiCDC | 8300 | TiCDC communication port |
| Monitoring | 9090 | Communication port for the Prometheus service |
| Monitoring | 20120 | Communication port for the NgMonitoring service |
| Node_exporter | 9100 | Communication port for reporting system information from all TiDB cluster nodes |
| Blackbox_exporter | 9115 | Blackbox_exporter communication port. Used to monitor ports in the TiDB cluster. |
| Grafana | 3000 | Port for external web monitoring services and client (browser) access |
| Alertmanager | 9093 | Alert web service port |
| Alertmanager | 9094 | Alert communication port |