Resource relationships

The main entity used in Yandex MPP Analytics for PostgreSQL is a database cluster.

Each cluster consists of database hosts, which are virtual machines with DBMS servers deployed on them. A Greenplum® cluster contains:

• Two master hosts.
• Two or more segment hosts.

The primary master host (PRIMARY) accepts client connections and SQL queries and distributes them to the segment hosts for processing.

The standby master host (STANDBY) continuously replicates the primary one's data but accepts no user connections.

If the primary master fails, the standby one takes over. This way, a cluster with two master hosts continues handling queries if a single master fails.

Segment hosts have standalone DBMS's (segments) deployed on them. They store data fragments and perform most operations for handling queries. Each cluster segment has a replica, i.e., a mirror segment that is located on another host and stores a copy of the data from the main segment.

The number of segments is the same for each host. When expanding a cluster, you can increase the number of segments. They will be added to all hosts — both new and existing ones. You cannot add segments to existing hosts without expanding the cluster.

Greenplum® cluster hosts are cloud VMs. Such VMs can reside on:

• Regular Yandex Cloud hosts:

  These are physical servers for hosting cluster VMs. They are randomly selected from a pool of available hosts that meet the selected cluster configuration.

• Dedicated Yandex Cloud hosts:

  These are physical servers reserved exclusively for your VMs. VMs on dedicated hosts have all the features of regular VMs. In addition, they are physically isolated from other users' VMs and have access to the whole volume of the physical server's local disks.

  Dedicated hosts are selected from dedicated host groups specified when creating a cluster. You must first create a group of dedicated hosts in Yandex Compute Cloud.

  To learn more, see Dedicated host.

All Greenplum® cluster hosts are placed in the same availability zone, ru-central1-a, ru-central1-b, or ru-central1-d.

When creating a cluster, specify:

• Host class: Template for deploying cluster hosts. For a list of available host classes and their characteristics, see Host classes.

• Environment: Environment where the cluster will be deployed:

  • PRODUCTION: For stable versions of your applications.
  • PRESTABLE: For testing purposes. The prestable environment is similar to the production environment and likewise covered by an SLA, but it is the first to get new features, improvements, and bug fixes. In the prestable environment, you can test new versions for compatibility with your application.

Be mindful of what is what is controlled by the service, and what by the Yandex Cloud customer. Understanding these control zones will help you use your cloud resources effectively and avoid potential database-related problems. For more information, see Zones of control between managed database (MDB) service users and Yandex Cloud.

Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries.