forked from docs/doc-exports
Wuwan, Qi
050b395397
Reviewed-by: Kacur, Michal <michal.kacur@t-systems.com> Co-authored-by: Wuwan, Qi <wuwanqi1@noreply.gitea.eco.tsi-dev.otc-service.com> Co-committed-by: Wuwan, Qi <wuwanqi1@noreply.gitea.eco.tsi-dev.otc-service.com>
19 lines
1.9 KiB
HTML
19 lines
1.9 KiB
HTML
<a name="css_01_0170"></a><a name="css_01_0170"></a>
|
|
|
|
<h1 class="topictitle1">Best Practices</h1>
|
|
<div id="body0000001082064357"><p id="css_01_0170__en-us_topic_0000001223914376_p8060118">This section describes how to switch from the primary cluster to the secondary cluster when the primary cluster is faulty.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p6766124611294">1. If the synchronization of specified indexes has been configured between the primary and secondary clusters.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p1448114503128">(1) 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.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p152332035352">(2) After the primary cluster recovers, call the index synchronization API to synchronize data from the secondary cluster to the primary cluster.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p146411933133316">2. If the matching pattern for index synchronization has been established between the primary and secondary clusters.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p2080111319459">(1) Call the API for deleting the created matching pattern for index synchronization in the secondary cluster.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p18516811194511">(2) Call the API for stopping index synchronization on the secondary cluster (using <strong id="css_01_0170__b15901219132713">*</strong> for matching). In this case, the read and write traffic can be switched to the secondary cluster.</p>
|
|
<p id="css_01_0170__en-us_topic_0000001223914376_p551611110453">(3) After the primary cluster recovers, call the index synchronization API to synchronize data from the secondary cluster to the primary cluster.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0161.html">Read/Write Splitting</a></div>
|
|
</div>
|
|
</div>
|
|
|