Open search page
Hello, I’m DocuDroid!
Open Ask AI page
Submitting feedback
Thank you for rating our AI Search!
We would be grateful if you could share your thoughts so we can improve our AI Search for you and other readers.
GitHub

Network requirements for Greengage DB installation

Andrey Aksenov

This topic describes the network requirements for Greengage DB (based on Greenplum) installation.

General network requirements

  • Greengage DB requires one or more dedicated and separate peer-to-peer Interconnect networks for internal cluster communication.

  • The recommended Ethernet speed is 10 Gbps or faster.

  • NIC bonding is recommended if a cluster host has multiple network interfaces.

  • The recommended maximum transmission unit (MTU) for Interconnect networks is 9000 bytes (jumbo frame MTU).

    NOTE

    The MTU size should also be configured in the following locations:

    • The operating system’s MTU settings for network interfaces.

    • The Greengage DB gp_max_packet_size server configuration parameter. The default maximum packet size is 8192 bytes, which assumes a jumbo frame MTU.

Internet and transport protocols

  • All cluster hosts should have an IP address and the ability to communicate with each other.

  • Greengage DB can use either IPv4 or IPv6 protocols.

  • Ping access to all cluster hosts should be enabled (ICMP protocol).

  • Greengage DB uses both TCP and UDP for its services. See Ports to learn more about specific ports that should be open.

Ports

All ports listed below should be open on the respective hosts. If you use a firewall, add these ports to the exception list.

Service Host type Port / Protocol Description

Master SQL client connection

Master and standby

5432 / TCP

An SQL client connection port on the Greengage DB master host. Supports clients that use the PostgreSQL libpq API

Standby master replicator

Master and standby

1025-65535 / TCP

Ports used to replicate the master log to the standby master

Secure Shell (SSH)

Master, standby, and segments

22 / SSH

Many Greengage DB utilities, such as gpssh, gpscp, and gpssh-exkeys, use SSH (Secure Shell) and SCP (Secure Copy Protocol) to manage a cluster and transfer files between hosts

Interconnect

Master, standby, and segments

1025-65535 / UDP

The Interconnect transports database tuples between segments during query execution. For the exact ports, refer to the gp_segment_configuration system table

Gpperfmon agents

Master, standby, and segments

8888 / TCP

The connection port for gpperfmon agents (gpmmon and gpsmon) running on cluster hosts. You can configure this port by setting the gpperfmon_port parameter in postgresql.conf on master and segment hosts

PXF

Segments

5888 / TCP

The PXF Java service runs on port 5888 by default on each Greengage DB segment host

Backup completion notification

Master and standby

25, 587 / SMTP

The gpbackup utility can optionally send an email to a list of addresses after a backup is completed. The SMTP service must be enabled on the Greengage DB master host

gpfdist

Segments or external hosts

8080 / HTTP

The gpfdist file serving utility can run on Greengage DB segment hosts or external hosts. You can specify the port range with the -p (start port) and -P (end port) options when starting the server. The default start port is 8080

gpload

Segments or external hosts

8000-9000 / HTTP

The gpload utility runs one or more instances of gpfdist with ports or port ranges specified in the configuration file. The 8000-9000 range is used by default and can be changed
Previous
Software
Next
Pre-installation configuration