forked from docs/doc-exports
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: zhengxiu <zhengxiu@huawei.com> Co-committed-by: zhengxiu <zhengxiu@huawei.com>
19 lines
1.7 KiB
HTML
19 lines
1.7 KiB
HTML
<a name="EN-US_TOPIC_0000001933159158"></a><a name="EN-US_TOPIC_0000001933159158"></a>
|
|
|
|
<h1 class="topictitle1">Can I Stop a CSS Cluster?</h1>
|
|
<div id="body0000001390862541"><p id="EN-US_TOPIC_0000001933159158__p1971310267423">To stop a CSS cluster, you delete it. If you want to stop a cluster upon completion of a cluster migration, stop all services in the source cluster, and confirm that all data has been migrated to the destination cluster. Then delete the source cluster. You can stop services in the source cluster in the following ways:</p>
|
|
<ul id="EN-US_TOPIC_0000001933159158__ul6264636113117"><li id="EN-US_TOPIC_0000001933159158__li2026483611314">If the cluster version in use supports the flow control function, you can enable one-click traffic blocking to block traffic everywhere except the O&M interface, rejecting all requests.</li><li id="EN-US_TOPIC_0000001933159158__li1964919399313">If your cluster version in use does not support traffic control, you can disable read and write for all service indexes instead. For example, if all service indexes start with <strong id="EN-US_TOPIC_0000001933159158__b113691344161215">log</strong>, run the following command on the <span class="uicontrol" id="EN-US_TOPIC_0000001933159158__uicontrol836912443129"><b>Dev Tools</b></span> page of Kibana:<pre class="screen" id="EN-US_TOPIC_0000001933159158__screen1166184595414">PUT <em id="EN-US_TOPIC_0000001933159158__i14817134210394">log</em>*/_settings
|
|
{
|
|
"index.blocks.read": true,
|
|
"index.blocks.write": true,
|
|
"index.blocks.metadata": true
|
|
}</pre>
|
|
</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0137.html">Managing CSS Clusters</a></div>
|
|
</div>
|
|
</div>
|
|
|