Network ports
The ports that a MooseFS cluster uses, who connects to each of them and which option moves each port. Every connection is TCP.
Ports that a daemon listens on
| Port | Listens | Connects to it | What it carries | Expected traffic | Option |
|---|---|---|---|---|---|
9419 | Master Server | Metaloggers, supervisors, and following Master Servers PRO (PRO Edition only) | Metadata and the changelog stream, and the state of the Master Servers that a supervisor reads and changes. | Metadata: low, with a peak when a Metalogger downloads the whole image. | MATOML_LISTEN_PORT in mfsmaster.cfg |
9420 | Master Server | Chunkservers | Chunkserver registration, what a Chunkserver reports about its chunks, and the orders that it gets: replicate, delete or duplicate a chunk. | Control: low, with a burst while a Chunkserver registers. | MATOCS_LISTEN_PORT in mfsmaster.cfg |
9421 | Master Server | Clients, mfscli, and the GUI server | Everything that a mount does with metadata, the session of the mount, and the cluster state that the GUI and mfscli display. | Metadata: low to moderate. The traffic grows with the number of operations. | MATOCL_LISTEN_PORT in mfsmaster.cfg |
9422 | Chunkserver | Clients, other Chunkservers, the GUI and mfscli | Chunk data on read and write, replication between Chunkservers, and the charts of a single Chunkserver. | Data: high to very high. The throughput of the cluster goes here. | CSSERV_LISTEN_PORT in mfschunkserver.cfg |
9425 | GUI server | Web browsers, and a Prometheus scraper on /metrics | The monitoring interface over HTTP, the metrics endpoint included. | Monitoring: minimal. The traffic grows with the number of open browsers, with how often Prometheus scrapes and with how much each scrape asks for, not with the amount of data stored. | GUISERV_LISTEN_PORT in mfsgui.cfg |
The traffic column is indicative. The real traffic on a port depends on the amount of data, the size of the files, the number of copies that each chunk has and the way the cluster is used.
Each of these ports has a *_LISTEN_HOST option in the configuration file that sets the port. The host option decides the addresses that the daemon accepts connections on. * stands for every address of the machine.
The MooseFS packages carry these numbers. A MooseFS built with another port base moves all the ports at once. See values set at build time.
Where a component connects
| Component | Connects to | Port | Set by |
|---|---|---|---|
| Chunkserver | Master Server | 9420 | MASTER_PORT in mfschunkserver.cfg |
| Chunkserver, as a supervisor of the Master Servers PRO (PRO Edition only) | Master Server | 9419 | MASTER_CONTROL_PORT in mfschunkserver.cfg |
| Metalogger | Master Server | 9419 | MASTER_PORT in mfsmetalogger.cfg |
| Following Master Server PRO (PRO Edition only) | leading Master Server | 9419 | The port that the Master Server listens on itself |
mfsmount, mfsbdev | Master Server | 9421 | -o mfsport=PORT, -P PORT |
mfssupervisor | Master Server | 9419 | -P PORT |
mfscli | Master Server | 9421 | -P PORT |
| Client, Chunkserver | Chunkserver | 9422 | The address that the Master Server hands out |
A Chunkserver reports the port that it listens on when it registers. The Master Server passes that address on to the clients and to the other Chunkservers. CSSERV_LISTEN_PORT is therefore set in one place only.
A mount listens as well: mfsmount opens a proxy for the command line tools on the loopback address. The system picks the port number of the proxy. Nothing outside that machine connects to it.