Forum Discussion
API_User
2 years agoLevel 9
Thank you for reaching out.
Within the Fabric connection creation process, we can create redundant connections to service profiles which requires redundancy. If the profile is not enforcing redundancy, we can expect the error mentioned above.
The current GCP profile setup has caused this confusion. In order to achieve redundancy for GCP connectivity, we are expected to create connections to two separate service profiles, each associated with zone 1 and zone 2. Since an individual service profile independently does not enforce redundancy, we create a connection with `redundancy.priority` as `PRIMARY`. When a connection is created with priority `SECONDARY`, an error is expected.
Regards,
Fabric Development Team
Within the Fabric connection creation process, we can create redundant connections to service profiles which requires redundancy. If the profile is not enforcing redundancy, we can expect the error mentioned above.
The current GCP profile setup has caused this confusion. In order to achieve redundancy for GCP connectivity, we are expected to create connections to two separate service profiles, each associated with zone 1 and zone 2. Since an individual service profile independently does not enforce redundancy, we create a connection with `redundancy.priority` as `PRIMARY`. When a connection is created with priority `SECONDARY`, an error is expected.
Regards,
Fabric Development Team
Related Content
- 3 years ago
- 3 years ago