Monitoring the state of a Greenplum® cluster and hosts
Data on cluster and host states are available in the management console. You can view them on the Monitoring tab of the cluster management page or in Yandex Monitoring.
Diagnostic information about cluster states is presented as graphs.
New data for charts is received every 15 seconds.
Note
The most appropriate multiple units (MB, GB, and more) are automatically used in charts.
Monitoring cluster state
To view detailed information about the Managed Service for Greenplum® cluster state:
- Go to the folder page
and select Managed Service for Greenplum. - Click the name of the cluster you need and select the
Monitoring tab. -
To get started with Yandex Monitoring metrics, dashboards, or alerts, click Open in Monitoring in the top panel.
The page displays the following charts:
-
Alive hosts: Cluster host functionality.
-
Alive segments: Primary and backup master as well as primary and mirror segment functionality.
-
Connections: Number of DB connections in each state:
- Active: Active.
- Waiting: Waiting.
- Idle: Idle.
- Idle in transaction: Idle in a transaction.
- Aborted: Terminated.
-
Group resource cpu: Processor core workload by process group:
- admin_group: In the administrative group.
- default_group: In the default group.
-
Group resource memory: Bytes of RAM used by process group:
- admin_group: In the administrative group.
- default_group: In the default group.
-
Master: Definition of the primary master host.
-
Master replication lag: Master replication delay (in bytes).
-
Master replication state: Master replication condition.
-
Segment health: Number of segments with various levels of performance:
- total: Everything.
- not sync: Unsynced.
- down: Unavailable.
- not prefer role: Non-preferred.
-
Spill files count: Number of temporary files.
-
Spill files size: Total size of temporary files (in bytes).
-
Xid wraparound: Utilization of sequence of transaction IDs
(as a percentage). -
Background activities: Group of charts presenting information about background processes:
-
Tables vacuum age: Number of custom tables that were vacuumed N days ago.
-
Tables analyze age: Number of custom tables for which statistics were collected N days ago.
-
Expansion progress: Progress of data redistribution when expanding a cluster:
- Tables: Percentage of processed tables.
- Bytes: Percentage of redistributed data bytes.
Note
This chart will show the current progress, even if the data redistribution was started not as a background process.
-
Monitoring the state of hosts
To view detailed information about the state of individual Managed Service for Greenplum® hosts:
- Go to the folder page
and select Managed Service for Greenplum. - Click the name of the cluster you need and select the
Hosts → Monitoring tab. - Select the host from the drop-down list.
This page displays charts showing the workload of an individual cluster host (master or segment):
- CPU: Load on processor cores. As the load goes up, the
Idle
value goes down. - Disk IOPS in progress: Number of pending disk operations.
- Disk io time: Duration of disk operations.
- Disk read and write: Amount of data in disk operations (in bytes).
- Disk read and write time: Duration of disk reads and writes.
- Disk usage: Disk space usage (two charts are displayed, in bytes and %).
- Memory usage: Use of RAM, in bytes. At high loads, the
Free
value goes down, while the other values go up. - Network: Amount of network traffic (in bytes).
Monitoring network state
To view detailed information about the Managed Service for Greenplum® cluster network state:
- Go to the folder page
and select Managed Service for Greenplum. - Click the name of the cluster you need and select the
Monitoring → Network tab.
This page displays the following charts:
-
Interfaces:
- Сlient Interface Packets: Number of received and sent packets on the client network interface.
- Сlient Interface Packets: Total size of received and sent data on the client network interface (in bytes).
- Client Interface Drops and Errors: Number of errors and drops on the client network interface when sending or transmitting packets.
- Service Interface Packets: Number of received and sent packets on the service network interface.
- Service Interface Packets: Total size of received and sent data on the service network interface (in bytes).
- Service Interface Drops and Errors: Number of errors and drops on the service network interface when sending or transmitting packets.
-
CPU:
- CPU Usage: Usage of processor cores (percentage).
-
Ping and SSH response time:
- Host Ping Average Response: Average ping response time (in milliseconds).
- Host Ping Packet Loss: Lost ping packets (percentage).
- Host SSH Response Time: Response time when connecting via SSH (in milliseconds).
-
TCP counters:
- TcpActiveConnection: Number of active TCP connections in the
ESTABLISHED
orCLOSE-WAIT
state. - TCP Errors: Number of errors when transmitting TCP packets.
- TcpEstabPresets: Number of times TCP connections have made a direct transition to the
CLOSED
state from either theESTABLISHED
orCLOSE-WAIT
state. - TCP Retransmission: Number of retransmitted TCP packets.
- TcpActiveConnection: Number of active TCP connections in the
-
ICMP Counters:
- IcmpErrors: Number of ICMP error messages.
- Icmp6PacketsTooBig: Number of ICMPv6 Packet Too Big messages.
- IcmpDestUnreached: Number of ICMP and ICMPv6 Destination Unreachable messages.
-
UDP counters:
- UdpSndbufErrors: Number of buffer errors when sending UDP packets.
- UDP Datagrams: Number of UDP packets.
- UdpRcvbufErrors: Number of buffer errors when receiving UDP packets.
- UDP NoPorts: Number of UDP packets received without a listener on the destination port.
-
IP:
- IpMulticastPackets: Number of received and sent multicast packets.
- Ip6 Neighbor Discovery: Number of sent requests and router advertisements.
- IpBroadcastPackets: Number of received and sent broadcast packets.
- Ip6NoRoutes: Number of IPv6 packets discarded because no route could be found.
PXF monitoring
To view detailed information about the PXF state:
- Go to the folder page
and select Managed Service for Greenplum. - Click the name of the cluster you need and select the
Monitoring → PXF tab.
This page displays the following charts:
-
Liveness: PXF state on hosts.
-
Connections: Number of connections.
-
Log messages: Number of messages of the
warn
,trace
,info
,fatal
,error
, anddebug
types. -
File handles: Number of files opened during the PXF process.
-
JVM memory: JVM PXF memory usage (in GB).
-
PXF threads: Number of PXF threads.
-
Sent data: Amount of sent data.
-
Sent records: Number of records send by PXF.
-
JVM threads: Number of JVM PXF threads.
-
PXF Busy threads: Number of busy PXF threads.
-
Received data: Amount of received data.
-
Received records: Number of records received by PXF.
Integration with Yandex Monitoring
To configure cluster and host state indicator alerts:
- In the management console
, select the folder with the cluster you want to configure alerts for. - In the list of services, select
Monitoring. - Under Service dashboards, select:
- Managed Service for Greenplum® — Cluster Overview to configure cluster alerts.
- Managed Service for Greenplum® — Host Overview to configure host alerts.
- In the indicator chart, click
and select Create alert. - If the chart shows multiple indicators, select a data query to generate a metric and click Continue. For more information about the query language, see the Yandex Monitoring documentation.
- Set the
Alarm
andWarning
thresholds for notifications. - Click Create alert.
To have other cluster health indicators monitored automatically:
- Create an alert.
- Add a status metric.
- In the alert parameters, set up your alert thresholds.
For a complete list of supported metrics, see the Monitoring documentation.
Cluster state and status
The State of a cluster shows the health of its hosts, while the Status shows whether the cluster is started, stopped, or is at an intermediate stage.
To view a cluster's state and status:
- Go to the folder page
and select Managed Service for Greenplum. - Hover over the indicator in the Availability column in the required cluster row.
Cluster states
State | Description | Suggested actions |
---|---|---|
ALIVE | Cluster is operating normally. | No action is required. |
DEGRADED | Cluster is not running at its full capacity: the state of at least one of the hosts is other than ALIVE . |
Run the diagnostics:
|
DEAD | The cluster is down: none of its hosts are running. | Make a support request
|
UNKNOWN | Cluster state is unknown. | Make a support request
|
Cluster statuses
Status | Description | Suggested actions |
---|---|---|
CREATING | Preparing for the first launch | Wait a while and get started. The time it takes to create a cluster depends on the host class. |
RUNNING | Cluster is operating normally | No action is required. |
STOPPING | Stopping cluster | After a while, the cluster status will change to STOPPED and the cluster will be disabled. No action is required. |
STOPPED | Cluster stopped | Start the cluster to get it running again. |
STARTING | Starting the cluster that was stopped earlier | After a while, the cluster status will change to RUNNING . Wait a while and get started. |
UPDATING | Updating the cluster status | After the update is completed, the cluster status will change to RUNNING . Wait a while and get started. |
ERROR | An error occurred that does not allow the cluster to continue working | Run the initial diagnostics:
|
STATUS_UNKNOWN | Cluster is unable to determine its own status | Run the initial diagnostics:
|
Greenplum® and Greenplum Database® are registered trademarks or trademarks of VMware, Inc. in the United States and/or other countries.