Troubleshooting Flexible Server
Refer to this documentation for troubleshooting Azure environments using Flexible Server.
Capacity limitation related warning during Flexible Server upgrade
Problem:
A capacity related validation warning is shown during the upgrade from Azure Single Server to Flexible Server.
Solution:
- File an Azure Support Ticket, specifying the Azure subscription and region that is used for the Cloudera setup. Microsoft Azure support will ensure that the necessary capacity is allocated to unblock provisioning Flexible Server same-zone HA database instances.
- Once the capacity has been increased, retry the Single Server to Flexible Server upgrade operation.
Missing default outbound access
Problem:
Data Lake provisioning failed due to missing outbound access.
Solution:
By default, Single Server utilizes service endpoints (Azure Database for PostgreSQL server - Microsoft.Sql) that provide secure and direct connectivity to DB service over an optimized route over the Azure backbone network from the Virtual Machines, but that is not the case with Flexible Server. This means that there are certain cases when you have to explicitly ensure that outbound (i.e. egress) network connectivity from the selected Virtual Network is set up using NAT-Gateway, UDR, or similar. If you are using a public Flexible Server, make sure that port 5432 is open for outbound traffic.
This requirement is applicable in the following conditions:
-
An existing network is being used.
-
Create Public IP is disabled.
-
Public Endpoint Gateway is disabled.
The lack of default outbound access can be mitigated by using private setup or using public IPs instead.
For more information, see Default outbound access in Azure.
