Port 1862: MySQL Cluster Manager Agent

What Port 1862 Does

Port 1862 carries traffic for the MySQL Cluster Manager (MCM) Agent. When you run MySQL Cluster Manager, it deploys a lightweight agent process on each host in your cluster. Those agents listen on port 1862. The MCM client talks to them to start, stop, configure, and monitor MySQL Cluster (NDB Cluster) nodes.

Think of it this way: MySQL Cluster is the database itself, spread across multiple machines. MySQL Cluster Manager is the control plane that orchestrates all those machines. Port 1862 is the wire between the conductor and the musicians.

What MySQL Cluster Manager Does

MySQL NDB Cluster is MySQL's high-availability, high-redundancy clustering solution. It runs across multiple hosts simultaneously — data nodes, management nodes, SQL nodes — and keeping all of them coordinated manually is painful.

MySQL Cluster Manager automates that coordination. It can:

• Start and stop individual nodes or entire clusters
• Perform rolling upgrades without downtime
• Back up and restore cluster data
• Reconfigure cluster parameters across all nodes at once
• Monitor cluster health and topology

The agent on port 1862 is what makes this possible. Each host reports its status and accepts commands through this channel.

IANA Registration

Port 1862 was registered with IANA on December 8, 2009, for TCP and UDP, under the service name mysql-cm-agent.¹ The registrant is Andrew Morgan of MySQL/Sun Microsystems (later Oracle).

Note: Some third-party port databases still list port 1862 as "unassigned" or associate it with an obscure "techra-server" entry. Those databases are wrong. The IANA registry is the authoritative source, and it has been clear since 2009: this port belongs to MySQL Cluster Manager.

Who Uses This Port

Port 1862 only appears on machines running MySQL Cluster Manager — which means it's almost exclusively found in enterprise environments running high-availability MySQL NDB Cluster deployments. If you're running a standard single-server MySQL installation, you'll never see port 1862.

Security Considerations

Because MySQL Cluster Manager controls your entire database cluster, port 1862 should never be exposed to untrusted networks. Access should be:

• Firewalled to only allow connections from authorized MCM client hosts
• Restricted to internal administrative networks
• Not accessible from the public Internet under any circumstances

An attacker with access to port 1862 could potentially stop database nodes, alter cluster configuration, or disrupt your entire database infrastructure.

How to Check What's Listening on This Port

If you see port 1862 open on a host and want to verify what's using it:

On Linux:

ss -tlnp | grep 1862
# or
lsof -i :1862

On macOS:

lsof -i :1862

On Windows:

netstat -ano | findstr :1862

If MySQL Cluster Manager is running, you'll see the mcmd (MCM daemon) process. If something else is listening here, investigate — it shouldn't be.

Related Ports

MySQL NDB Cluster uses several ports you'll often see alongside 1862: