Greenplum Database Ports and Protocols

A newer version of this documentation is available. Use the version menu above to view the most up-to-date release of the Greenplum 5.x documentation.

Greenplum Database Ports and Protocols

Lists network ports and protocols used within the Greenplum cluster.

Greenplum Database clients connect with TCP to the Greenplum master instance at the client
connection port, 5432 by default. The listen port can be reconfigured in the
postgresql.conf configuration file. Client connections use the
PostgreSQL libpq API. The psql command-line interface, several Greenplum
utilities, and language-specific programming APIs all either use the libpq library directly or
implement the libpq protocol internally.

Each segment instance also has a client connection port, used solely by the master instance
to coordinate database operations with the segments. The gpstate -p command,
executed on the Greenplum master, lists the port assignments for the Greenplum master and the
primary segments and mirrors. For example:

Additional Greenplum Database network connections are created for features such as standby
replication, segment mirroring, statistics collection, and data exchange between segments.
Some persistent connections are established when the database starts up and other transient
connections are created during operations such as query execution. Transient connections for
query execution processes, data movement, and statistics collection use available ports in the
range 1025 to 65535 with both TCP and UDP protocols.

Note: To avoid port conflicts between Greenplum Database and other applications when
initializing Greenplum Database, do not specify Greenplum Database ports in the range
specified by the operating system parameter net.ipv4.ip_local_port_range. For
example, if net.ipv4.ip_local_port_range = 10000 65535, you could set the
Greenplum Database base port numbers to values outside of that
range:

Some add-on products and services that work with Greenplum Database have additional
networking requirements. The following table lists ports and protocols used within the
Greenplum cluster, and includes services and applications that integrate with Greenplum
Database.

The SQL client connection port for a segment instance. Each primary and mirror
segment on a host must have a unique port. Ports are assigned when the Greenplum
system is initialized or expanded. The gp_segment_configuration
system catalog records port numbers for each primary (p) or mirror (m) segment in the
port column. Run gpstate -p to view the ports in
use.

Segment mirroring port

varies, libpq

The port where a segment receives mirrored blocks from its primary. The port is
assigned when the mirror is set up. The gp_segment_configuration
system catalog records port numbers for each primary (p) or mirror (m) segment in the
port column. Run gpstate -p to view the ports in
use.

Many Greenplum utilities use scp and ssh to transfer files between hosts and
manage the Greenplum system within the cluster.

gphdfs (deprecated)

TCP 8020

The gphdfs protocol allows access to data in a Hadoop file system via Greenplum
external tables. The URL in the LOCATION clause of the CREATE
EXTERNAL TABLE command specifies the host address and port number for the
Hadoop namenode service.

Greenplum Platform Extension Framework (PXF)

TCP 5888

The PXF Java service runs on port number 5888 on each Greenplum Database segment
host.

Greenplum Command Center (GPCC)

TCP 28080, HTTP/HTTPS, WebSocket (WS), Secure WebSocket (WSS)

The GPCC web server (gpccws process) executes on the Greenplum Database master
host or standby master host. The port number is configured at installation
time.

TCP 8899, rcp port

A GPCC agent (ccagent process) on each Greenplum Database segment host connects
to the GPCC rpc backend at port number 8899 on the GPCC web server host.

UNIX domain socket, agent

Greenplum Database processes transmit datagrams to the GPCC agent (ccagent
process) on each segment host using a UNIX domain socket.

GPText

TCP 2188 (base port)

ZooKeeper client ports. ZooKeeper uses a range of ports beginning at the base port
number. The base port number and maximum port number are set in the GPText installation
configuration file at installation time. The default base port number is 2188.

TCP 18983 (base port)

GPText (Apache Solr) nodes. GPText nodes use a range of ports beginning at the base
port number. The base port number and maximum port number are set in the GPText installation
configuration file at installation time. The default base port number is 18983.

EMC Data Domain and DD Boost

TCP/UDP 111, NFS portmapper

Used to assign a random port for the mountd service used by NFS and DD Boost. The
mountd service port can be statically assigned on the Data Domain server.

TCP 2052

Main port used by NFS mountd. This port can be set on the Data Domain system
using the nfs set mountd-port command .

TCP 2049, NFS

Main port used by NFS. This port can be configured using the nfs set
server-port command on the Data Domain server.

TCP 2051, replication

Used when replication is configured on the Data Domain system. This port can be
configured using the replication modify command on the Data Domain
server.

Symantec NetBackup

TCP/UDB 1556, veritas-pbx

The Symantec NetBackup client network port.

TCP 13724, vnetd

Symantec NetBackup vnetd communication port.

Pgbouncer connection pooler

TCP, libpq

The pgbouncer connection pooler runs between libpq clients and Greenplum (or
PostgreSQL) databases. It can be run on the Greenplum master host, but running it on a
host outside of the Greenplum cluster is recommended. When it runs on a separate host,
pgbouncer can act as a warm standby mechanism for the Greenplum master host, switching
to the Greenplum standby host without requiring clients to reconfigure. Set the client
connection port and the Greenplum master host address and port in the
pgbouncer.ini configuration file.