Starting from February 8, 2021, AnalyticDB for PostgreSQL allows you to configure multiple coordinator nodes.
You can add multiple coordinator nodes to an AnalyticDB for PostgreSQL instance to push beyond the limits of its original single-coordinator node architecture. If the compute nodes permit, the number of connections and the I/O capabilities linearly increase with the number of coordinator nodes, and overall system performance improves. However, if you use multiple coordinator nodes within an instance, the cluster endpoint of the instance has limits. For your convenience, AnalyticDB for PostgreSQL provides both the primary and cluster endpoints. You can choose an endpoint to use based on your compatibility and performance considerations. If you have questions, join the DingTalk group 11700737 for technical support.
If you select more than 8 compute units (CUs) of coordinator node resources when you create an AnalyticDB for PostgreSQL instance or change coordinator node specifications, a cluster endpoint is created besides the primary endpoint.
Primary endpoint: Requests that are initiated from this type of endpoints are forwarded to the primary coordinator node. Secondary coordinator nodes do not handle requests. If you choose to use this type of endpoints, the capabilities of the system are fully compatible with an AnalyticDB for PostgreSQL instance that has a single coordinator node.
Cluster endpoint: Requests that are initiated from this type of endpoints are forwarded to the primary coordinator node and secondary coordinator nodes because Server Load Balancer (SLB) is automatically connected.