What Runs on This Port
Port 1186 is the official IANA-assigned port for MySQL Cluster Manager (also called NDB Cluster management). It's the control plane for MySQL NDB Cluster—a distributed database system that spreads data across multiple servers for redundancy and performance.
Every node in a MySQL Cluster—data nodes that store the actual data, SQL nodes that handle queries—needs to talk to the management node. That conversation happens on port 1186.
How It Works
MySQL NDB Cluster uses a shared-nothing architecture. Data is partitioned across multiple data nodes, and SQL nodes can query any of them. But someone has to coordinate this—track which nodes are alive, which ones have which data, handle configuration changes, orchestrate restarts.
That's the management node's job. And port 1186 is where it listens.
When a cluster component starts up, it connects to the management node using a connection string that looks like this:
If you leave off the port number, it defaults to 1186. The MySQL documentation notes: "This port should always be available on the network because it has been assigned by IANA for this purpose."1
That's a rare acknowledgment. IANA assigns thousands of ports, but most documentation doesn't explicitly call out the assignment as a reason for reliability. Here, it matters. If your management node can't be reached on 1186, your entire cluster can't coordinate.
The Architecture
An NDB Cluster has three types of nodes:
Management nodes run ndb_mgmd and coordinate the cluster. They don't store data, they don't run queries—they just orchestrate. Port 1186 is where they listen.
Data nodes run ndbd or ndbmtd and actually store the distributed data. They connect to the management node on startup and stay connected for coordination.
SQL nodes run mysqld with the NDB storage engine. They're regular MySQL servers, but they talk to data nodes for actual storage. They also check in with the management node on port 1186 to learn the cluster topology.
All of this traffic—heartbeats, configuration updates, node status changes—flows through port 1186.
Why This Port Exists
MySQL NDB Cluster was originally developed by Ericsson for telecom applications that couldn't afford downtime. Phone switches need databases that don't go down when a server fails. The architecture they built spread data across nodes so that no single failure kills the system.
But distributed systems need coordination. The management node on port 1186 is that coordinator. It's not in the data path—queries don't flow through it. But without it, the cluster can't start, can't reconfigure, can't recover from failures.
Port 1186 was officially registered with IANA for this purpose, ensuring it wouldn't conflict with other services.2
Security Considerations
Port 1186 carries cluster control traffic. If someone gains access to your management node, they can reconfigure your cluster, shut down nodes, or learn your entire database topology.
Best practices:
- Firewall this port. Only cluster nodes should reach it. Client applications don't need direct access to the management node.
- Use internal networks. Cluster coordination traffic shouldn't cross the public Internet.
- Monitor connections. Unexpected connections to port 1186 mean someone's probing your cluster infrastructure.
The management protocol itself doesn't have built-in encryption. You're trusting network isolation to protect it.
Checking What's Listening
On Linux or macOS, check if something is listening on port 1186:
On a properly configured management node, you should see ndb_mgmd listening:
If you see this port open on a server that isn't supposed to be a MySQL Cluster management node, investigate. Either someone installed NDB Cluster, or something else is squatting on this port.
Related Ports
MySQL NDB Cluster uses several ports:
- Port 1186 (this port) — Management node coordination
- Port 3306 — Standard MySQL client connections (SQL nodes)
- Port 2202 — Default port for data node-to-data node communication (configurable)
The data nodes also open dynamic ports for transporter connections. Port 1186 is the only one with an official IANA assignment.
The Invisible Coordinator
If you're running a standard MySQL server, you'll never see port 1186. It only exists in NDB Cluster deployments—high-availability setups where data is distributed and redundant.
But for the systems that use it, this port is critical. It's the reason a cluster can lose a data node and keep running. The reason configuration changes propagate. The reason nodes know where to find each other.
It's not in the data path. But it's the control plane. And without it, the cluster is just a collection of disconnected servers.
Frequently Asked Questions About Port 1186
بۇ بەت پايدىلىق بولدىمۇ؟