Starting from February 8, 2021, AnalyticDB for PostgreSQL allows you to configure multiple coordinator nodes.

You can add multiple coordinator nodes to an 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 endpoints of the instance have limits. For your convenience, AnalyticDB for PostgreSQL provides endpoints for both the primary coordinator node and the instance. You can choose an endpoint to use based on your compatibility and performance considerations. If you have questions, join the DingTalk group for technical support or submit a ticket.

If you set more than one coordinator node when you create an AnalyticDB for PostgreSQL instance, separate endpoints are created for the primary coordinator node and the instance.

Endpoints of the primary coordinator node: Requests 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.

Endpoints of the instance: Requests 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.