forked from docs/doc-exports
Yang, Tong
3f5759eed2
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Yang, Tong <yangtong2@huawei.com> Co-committed-by: Yang, Tong <yangtong2@huawei.com>
22 lines
4.9 KiB
HTML
22 lines
4.9 KiB
HTML
<a name="mrs_01_0855"></a><a name="mrs_01_0855"></a>
|
|
|
|
<h1 class="topictitle1">Configuring Resources for a NodeManager Role Instance</h1>
|
|
<div id="body8662426"><div class="section" id="mrs_01_0855__en-us_topic_0000001219351223_sfd216f4a53f643f9b728da02006390a8"><h4 class="sectiontitle">Scenario</h4><p id="mrs_01_0855__en-us_topic_0000001219351223_a5c484ea295af4db29266b083e1d65b22">If the hardware resources (such as the number of CPU cores and memory size) of the nodes for deploying NodeManagers are different but the NodeManager available hardware resources are set to the same value, the resources may be wasted or the status may be abnormal. You need to change the hardware resource configuration for each NodeManager to ensure that the hardware resources can be fully utilized.</p>
|
|
</div>
|
|
<div class="section" id="mrs_01_0855__en-us_topic_0000001219351223_s974010afef9146ae9dac740d3f4f686e"><h4 class="sectiontitle">Impact on the System</h4><p id="mrs_01_0855__en-us_topic_0000001219351223_a878929f01da24ed8a777ecabbd8e0149">NodeManager role instances must be restarted for the new configuration to take effect, and the role instances are unavailable during restart.</p>
|
|
</div>
|
|
<div class="section" id="mrs_01_0855__en-us_topic_0000001219351223_s208eb2bfb56047aa928c3ba193d7ed09"><h4 class="sectiontitle">Prerequisites</h4><p id="mrs_01_0855__en-us_topic_0000001219351223_p202971136141013">You have logged in to Manager.</p>
|
|
</div>
|
|
<div class="section" id="mrs_01_0855__en-us_topic_0000001219351223_sd65b493a21d6478faefec5266189bb75"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_01_0855__en-us_topic_0000001219351223_ol778821044418"><li id="mrs_01_0855__en-us_topic_0000001219351223_li1178816103449"><span>Choose <strong id="mrs_01_0855__en-us_topic_0000001219351223_b205162549841647">Cluster</strong> > <em id="mrs_01_0855__en-us_topic_0000001219351223_i185107742941647">Name of the desired cluster</em> > <strong id="mrs_01_0855__en-us_topic_0000001219351223_b33464292841647">Services</strong> > <strong id="mrs_01_0855__en-us_topic_0000001219351223_b46224841441647">Yarn</strong> > <strong id="mrs_01_0855__en-us_topic_0000001219351223_b73636690341647">Instance</strong>.</span></li><li id="mrs_01_0855__en-us_topic_0000001219351223_li1978801054415"><span>Click the role instance name corresponding to the node where NodeManager is deployed, switch to <strong id="mrs_01_0855__en-us_topic_0000001219351223_b194640659541647">Instance Configuration</strong>, and select <strong id="mrs_01_0855__en-us_topic_0000001219351223_b72081477841647">All Configurations</strong>.</span></li><li id="mrs_01_0855__en-us_topic_0000001219351223_li378816109445"><span>Enter <strong id="mrs_01_0855__en-us_topic_0000001219351223_b493647282">yarn.nodemanager.resource.cpu-vcores</strong> in the search box, and set the number of vCPUs that can be used by NodeManager on the current node. You are advised to set this parameter to 1.5 to 2 times the number of actual logical CPUs on the node. Enter <strong id="mrs_01_0855__en-us_topic_0000001219351223_b168743465841647">yarn.nodemanager.resource.memory-mb</strong> in the search box, and set the physical memory size that can be used by NodeManager on the current node. You are advised to set this parameter to 75% of the actual physical memory size of the node.</span><p><div class="note" id="mrs_01_0855__en-us_topic_0000001219351223_note1078861074419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_01_0855__en-us_topic_0000001219351223_p16788131014414">Enter <strong id="mrs_01_0855__en-us_topic_0000001219351223_b1868700486">yarn.scheduler.maximum-allocation-vcores</strong> in the search box, and set the maximum number of available CPUs in a container. Enter <strong id="mrs_01_0855__en-us_topic_0000001219351223_b333833835">yarn.scheduler.maximum-allocation-mb</strong> in the search box, and set the maximum available memory of a container. The instance level cannot be changed. The parameter values need to be changed in the configuration of the Yarn service, and the Yarn service needs to be restarted for the changes to take effect.</p>
|
|
</div></div>
|
|
</p></li><li id="mrs_01_0855__en-us_topic_0000001219351223_li1678801017447"><span>Click <strong id="mrs_01_0855__en-us_topic_0000001219351223_b72643058341647">Save</strong>, and then click <strong id="mrs_01_0855__en-us_topic_0000001219351223_b32533986341647">OK</strong>. to restart the NodeManager role instance.</span><p><p id="mrs_01_0855__en-us_topic_0000001219351223_p18788410114414">A message is displayed, indicating that the operation is successful. Click <strong id="mrs_01_0855__en-us_topic_0000001219351223_b9458133002616">Finish</strong>. The NodeManager role instance is started successfully.</p>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_0851.html">Using Yarn</a></div>
|
|
</div>
|
|
</div>
|
|
|