forked from docs/doc-exports
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Reviewed-by: Rechenburg, Matthias <matthias.rechenburg@t-systems.com> Co-authored-by: Yang, Tong <yangtong2@huawei.com> Co-committed-by: Yang, Tong <yangtong2@huawei.com>
25 lines
5.4 KiB
HTML
25 lines
5.4 KiB
HTML
<a name="admin_guide_000059"></a><a name="admin_guide_000059"></a>
|
|
|
|
<h1 class="topictitle1">Isolating a Host</h1>
|
|
<div id="body1529658735912"><div class="section" id="admin_guide_000059__s5cede81872d14da59f960f6aaa7823c2"><h4 class="sectiontitle">Scenario</h4><p id="admin_guide_000059__p199518595123">If a host is abnormal or faulty and cannot provide services or affects the cluster performance, you can remove the host from the available node in the cluster temporarily so that the client can access other available nodes.</p>
|
|
<div class="note" id="admin_guide_000059__note262313511217"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="admin_guide_000059__p462318519116">Only non-management nodes can be isolated.</p>
|
|
</div></div>
|
|
</div>
|
|
<div class="section" id="admin_guide_000059__saea25ffeca544dfcb53ed680cf0563be"><h4 class="sectiontitle">Impact on the System</h4><ul id="admin_guide_000059__en-us_topic_0046737064_ul38749291"><li id="admin_guide_000059__en-us_topic_0046737064_li13199299">After a host is isolated, all role instances on the host will be stopped, and you cannot start, stop, or configure the host and all instances on the host.</li><li id="admin_guide_000059__li151561648162012">For some services, after a host is isolated, some instances on other nodes do not work, and the service configuration status may expire.</li><li id="admin_guide_000059__en-us_topic_0046737064_li51684833">After a host is isolated, statistics about the monitoring status and indicator data of the host hardware and instances on the host cannot be collected or displayed.</li><li id="admin_guide_000059__li93991629114110">Retain the default SSH port (22) of the target node. Otherwise, the task described in this section will fail.</li></ul>
|
|
</div>
|
|
<div class="section" id="admin_guide_000059__section17216194419511"><h4 class="sectiontitle">Procedure</h4><ol id="admin_guide_000059__en-us_topic_0046737064_ol27924406"><li id="admin_guide_000059__en-us_topic_0046737064_li49993063"><span>Log in to <span id="admin_guide_000059__text15946118176">MRS</span> Manager.</span></li><li id="admin_guide_000059__li1060084165213"><span>Click <span class="menucascade" id="admin_guide_000059__menucascade9934105875016"><b><span class="uicontrol" id="admin_guide_000059__uicontrol492885895013">Hosts</span></b></span>.</span></li><li id="admin_guide_000059__en-us_topic_0046737064_li47284389"><span>Select the check box of the host to be isolated.</span></li><li id="admin_guide_000059__en-us_topic_0046737064_li22906320"><span>Select <strong id="admin_guide_000059__b53701818204">Isolate</strong> from the <strong id="admin_guide_000059__b13749101318200">More</strong> drop-down list.</span><p><p id="admin_guide_000059__en-us_topic_0046737064_p4830289">In the displayed dialog box, enter the password of the current login user and click <strong id="admin_guide_000059__b1970914405204">OK</strong>.</p>
|
|
</p></li><li id="admin_guide_000059__en-us_topic_0046737064_li31619754"><span>In the displayed confirmation dialog box, select "I confirm to isolate the selected hosts and accept possible consequences of service faults." Click <strong id="admin_guide_000059__b29982821145512">OK</strong>.</span><p><p id="admin_guide_000059__p19273163612318">Wait until the message "Operation succeeded" is displayed, and click <strong id="admin_guide_000059__b1130553312314">Finish</strong>.</p>
|
|
<p id="admin_guide_000059__en-us_topic_0046737064_p16142333">The host is successfully isolated and <strong id="admin_guide_000059__b181197469215">Running Status</strong> is <strong id="admin_guide_000059__b924645212117">Isolated</strong>.</p>
|
|
</p></li><li id="admin_guide_000059__li96481820144817"><span>Log in to the isolated host as user <strong id="admin_guide_000059__b3583254185118">root</strong> and run the <strong id="admin_guide_000059__b19441822173315">pkill -9 -u omm</strong> command to stop the processes of user <strong id="admin_guide_000059__b0505242527">omm</strong> on the node. Then run the <strong id="admin_guide_000059__b1137616532331">ps -ef | grep 'container' | grep '${BIGDATA_HOME}' | awk '{print $2}' | xargs -I '{}' kill -9 '{}' </strong> command to find and stop the container process.</span></li><li id="admin_guide_000059__li784913259481"><span>Cancel the isolation status of the host before using the host if you have rectified the host exception or fault.</span><p><p id="admin_guide_000059__p158562373613">On the <strong id="admin_guide_000059__b92691256135213">Hosts</strong> page, select the isolated host and choose <strong id="admin_guide_000059__b411816455314">More</strong> > <strong id="admin_guide_000059__b214718610534">Cancel Isolation</strong>.</p>
|
|
<div class="note" id="admin_guide_000059__note4577192716715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="admin_guide_000059__p757719277720">After the isolation is canceled, all role instances on the host are not started by default. To start role instances on the host, select the target host on the Hosts page and choose <strong id="admin_guide_000059__b624628175313">More</strong> > <strong id="admin_guide_000059__b115661430125314">Start All Instances</strong>.</p>
|
|
</div></div>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="admin_guide_000054.html">Host Maintenance Operations</a></div>
|
|
</div>
|
|
</div>
|
|
|