Shows the status of a running Greenplum Database system.
gpstate [-d <master_data_directory>] [-B <parallel_processes>]
[-s | -b | -Q \| -e\] \[-m \| -c] [-p] [-i] [-f] [-v | -q] | -x
[-l <log_directory>]
gpstate -? | -h | --help
The gpstate
utility displays information about a running Greenplum Database instance. There is additional information you may want to know about a Greenplum Database system, since it is comprised of multiple PostgreSQL database instances (segments) spanning multiple machines. The gpstate
utility provides additional status information for a Greenplum Database system, such as:
$MASTER_DATA_DIRECTORY
will be used.
Show details on primary/mirror segment pairs that have potential issues. These issues include:
WAL sync remaining bytes
output field).Note
gpstate -e
does not display segment pairs that are in sync.
NoteYou must have
rsync
version 3.1.x or higher installed in order to view the tracking information for segments undergoing a differential recovery.
~/gpAdminLogs
.
The following output fields are reported by gpstate -s
for the master:
Output Data | Description |
---|---|
Master host | host name of the master |
Master postgres process ID | PID of the master database listener process |
Master data directory | file system location of the master data directory |
Master port | port of the master postgres database listener process |
Master current role | dispatch = regular operating mode utility = maintenance mode |
Greenplum array configuration type | Standard = one NIC per host Multi-Home = multiple NICs per host |
Greenplum initsystem version | version of Greenplum Database when system was first initialized |
Greenplum current version | current version of Greenplum Database |
Postgres version | version of PostgreSQL that Greenplum Database is based on |
Greenplum mirroring status | physical mirroring or none |
Master standby | host name of the standby master |
Standby master state | status of the standby master: active or passive |
The following output fields are reported by gpstate -s
for each primary segment:
Output Data | Description |
---|---|
Hostname | system-configured host name |
Address | network address host name (NIC name) |
Datadir | file system location of segment data directory |
Port | port number of segment postgres database listener process |
Current Role | current role of a segment: Mirror or Primary |
Preferred Role | role at system initialization time: Mirror or Primary |
Mirror Status | status of a primary/mirror segment pair: Synchronized = data is up to date on both Not in Sync = the mirror segment has not caught up to the primary segment |
Current write location | Location where primary segment is writing new logs as they come in |
Bytes remaining to send to mirror | Bytes remaining to be sent from primary to mirror |
Active PID | active process ID of a segment |
Master reports status as | segment status as reported in the system catalog: Up or Down |
Database status | status of Greenplum Database to incoming requests: Up, Down, or Suspended. A Suspended state means database activity is temporarily paused while a segment transitions from one state to another. |
The following output fields are reported by gpstate -s
for each mirror segment:
Output Data | Description |
---|---|
Hostname | system-configured host name |
Address | network address host name (NIC name) |
Datadir | file system location of segment data directory |
Port | port number of segment postgres database listener process |
Current Role | current role of a segment: Mirror or Primary |
Preferred Role | role at system initialization time: Mirror or Primary |
Mirror Status | status of a primary/mirror segment pair: Synchronized = data is up to date on both Not in Sync = the mirror segment has not caught up to the primary segment |
WAL Sent Location | Log location up to which the primary segment has sent log data to the mirror |
WAL Flush Location | Log location up to which the mirror segment has flushed the log data to disk |
WAL Replay Location | Log location up to which the mirror segment has replayed logs locally |
Bytes received but remain to flush | Difference between flush log location and sent log location |
Bytes received but remain to replay | Difference between replay log location and sent log location |
Active PID | active process ID of a segment |
Master reports status as | segment status as reported in the system catalog: Up or Down |
Database status | status of Greenplum Database to incoming requests: Up, Down, or Suspended. A Suspended state means database activity is temporarily paused while a segment transitions from one state to another. |
NoteWhen there is no connection between a primary segment and its mirror,
gpstate -s
displaysUnknown
in the following fields:
Bytes remaining to send to mirror
WAL Sent Location
WAL Flush Location
WAL Replay Location
Bytes received but remain to flush
Bytes received but remain to replay
The following output fields are reported by gpstate -f
for standby master replication status:
Output Data | Description |
---|---|
Standby address | hostname of the standby master |
Standby data dir | file system location of the standby master data directory |
Standby port | port of the standby master postgres database listener process |
Standby PID | process ID of the standby master |
Standby status | status of the standby master: Standby host passive |
WAL Sender State | write-ahead log (WAL) streaming state: streaming, startup,backup, catchup |
Sync state | WAL sender synchronization state: sync |
Sent Location | WAL sender transaction log (xlog) record sent location |
Flush Location | WAL receiver xlog record flush location |
Replay Location | standby xlog record replay location |
Show detailed status information of a Greenplum Database system:
gpstate -s
Do a quick check for down segments in the master host system catalog:
gpstate -Q
Show information about mirror segment instances:
gpstate -m
Show information about the standby master configuration:
gpstate -f
Display the Greenplum software version information:
gpstate -i