How it Works
When CDL is configured in SMF through the SMF Ops Center, SMF gets enabled to support multiple CDL datastore endpoints. You can configure the endpoints by specifying the IP addresses, ports, and assigning ratings to each endpoint. By default, SMF considers the local endpoint as the primary endpoint, which has the maximum rating. SMF performs CDL API operations on the primary endpoint. If this endpoint is unavailable, then SMF routes the operations to the next maximum rated endpoint. SMF keeps failing over to the accessible secondary endpoint or until all the configured secondaries are exhausted. It does not reattempt a query on the next rated endpoint if the endpoint is reachable but responds with error or timeout.
If SMF is unable to access any of the endpoints in the cluster, then CDL operation fails with the "Datastore Unavailable" error.
The following table lists the scenarios, expected behavior, and the related error responses from CDL.
Scenario |
Expected Behavior |
Error Response from CDL |
---|---|---|
All pods are active and healthy and trigger the CDL operations. |
CDL Create, Read, Update, Delete (CRUD) operations are not retried. |
Not applicable |
CDL endpoint pod restarts and triggers CDL operations. |
CDL CRUD operations are retried. |
CDL sends the following error responses with the error code:
|