Issue

Studio console on the secondary DDC does not fail over when the primary DDC goes down and shows error “Could not contact the configuration service”. The studio is able to load the machine catalog and delivery groups information only when the primary DDC is up.

Observation

Testing further it seems that when we put both the DDC in the primary zone, the “isPrimary” property is true for both the DDC, then things work fine in studio console. Even turning off one of the DDC the studio is able to retrieve the information from other DDC.  

Cause

• The current architecture assumes that the Primary Zone is highly available. Any interactions performed on a secondary zone can fail over to the Primary, but not vice versa.
• If the primary zone goes down for whatever reason, the secondary zones will continue to operate to the extent that the Connection Leasing behavior allows. However, things like Studio require a Controller in the primary zone to be working.
• Zones is really designed to reduce the amount of network traffic that traverses the WAN. It should not be considered as a DR solution

Solution

• DB servers and two DDCs are in the primary zone