Best Practices¶
This section describes how to switch from the primary cluster to the secondary cluster when the primary cluster is faulty.
If the synchronization of specified indexes has been configured between the primary and secondary clusters.
Call the API for stopping index synchronization in the secondary cluster. In this case, the read and write traffic can be switched to the secondary cluster.
After the primary cluster recovers, call the index synchronization API to synchronize data from the secondary cluster to the primary cluster.
If the matching pattern for index synchronization has been established between the primary and secondary clusters.
Call the API for deleting the created matching pattern for index synchronization in the secondary cluster.
Call the API for stopping index synchronization on the secondary cluster (using * for matching). In this case, the read and write traffic can be switched to the secondary cluster.
After the primary cluster recovers, call the index synchronization API to synchronize data from the secondary cluster to the primary cluster.