Skip to main content

Network requirements

MooseFS operates over a TCP/IP network. The faster and more reliable the network, the better the overall system performance. For optimal results, it’s recommended to connect all servers through the same switch, or at least minimize network latency as much as possible as latency can have a noticeable impact on system efficiency.

Open ports​

The following ports need to be open for MooseFS to function properly (these can be customized in the appropriate configuration files):

  • 9419..9421 – Master Server(s)
  • 9422 – Chunkservers
  • 9425 – CGI Server / Web GUI

MTU consistency​

For a MooseFS cluster to function reliably, MTU (Maximum Transmission Unit) consistency across all nodes in the network is essential. MTU defines the maximum size of a packet that can be transmitted over the network without fragmentation. Inconsistent MTU settings between nodes can lead to dropped packets, transmission delays, or subtle data integrity issues that are often difficult to diagnose.

When nodes in the cluster operate with different MTU values - especially when using jumbo frames - it can cause issues in communication between the Master Server, Chunkservers, and Clients. These problems may manifest as timeouts, intermittent connection failures, or degraded performance, particularly under high load or during large file transfers.

To prevent these issues, ensure that all interfaces involved in MooseFS communication are configured with the same MTU. This includes not only physical interfaces on each server but also any intermediate switches, routers, or VLAN configurations that could impact packet size limits.

A common and safe default MTU is 1500 bytes, which is widely supported and typically doesn't require any special configuration. However, if you're optimizing for performance and decide to use jumbo frames (e.g., 9000 bytes), make absolutely sure that every device in the communication path supports and is properly configured for the chosen MTU.

Consistency here isn't just a best practice - it's a requirement for a stable MooseFS deployment.