If a Node Becomes Unavailable, Does YugabyteDB Propagate Client Requests to Surviving Nodes? Or Do Clients Have to Handle That Retry Logic?` The availability of a node in a YugabyteDB cluster affects client requests. If clients are connected directly to the node, physical connections will be invalidated and connection pooling will adjust the minimum pool requirements for other nodes. Connection pooling manages new connections transparently to surviving nodes, allowing clients to retry failed transactions or set their own retry logic based on error codes. Passing multiple endpoints in a connection string (at least 2/3) helps create new client connections based on available endpoints, and having at least one endpoint per region is recommended for multi-region clusters.