07.Yarn生产环境核心参数配置案例

Leefs 2021-09-10 AM 1121℃ 0条

# 07.Yarn生产环境核心参数配置案例

### 前言

本篇通过一个案例来分析生产环境中，Yarn需要修改的配置参数。

### 一、案例

#### 1.1 需求

> 从1G数据中，统计每个单词出现次数。服务器3台，每台配置4G内存，4核CPU，4线程。

#### 1.2 需求分析

```
1G / 128m = 8个MapTask；1个ReduceTask；1个mrAppMaster
平均每个节点运行10个 / 3台 ≈ 3个任务（4	3	3）
```

#### 1.3 修改yarn-site.xml配置参数

```xml

<property>
	<description>The class to use as the resource scheduler.</description>
	<name>yarn.resourcemanager.scheduler.class</name>
	<value>org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler</value>
</property>

<property>
	<description>Number of threads to handle scheduler interface.</description>
	<name>yarn.resourcemanager.scheduler.client.thread-count</name>
	<value>8</value>
</property>

<property>
	<description>Enable auto-detection of node capabilities such as
	memory and CPU.
	</description>
	<name>yarn.nodemanager.resource.detect-hardware-capabilities</name>
	<value>false</value>
</property>

<property>
	<description>Flag to determine if logical processors(such as
	hyperthreads) should be counted as cores. Only applicable on Linux
	when yarn.nodemanager.resource.cpu-vcores is set to -1 and
	yarn.nodemanager.resource.detect-hardware-capabilities is true.
	</description>
	<name>yarn.nodemanager.resource.count-logical-processors-as-cores</name>
	<value>false</value>
</property>

<property>
	<description>Multiplier to determine how to convert phyiscal cores to
	vcores. This value is used if yarn.nodemanager.resource.cpu-vcores
	is set to -1(which implies auto-calculate vcores) and
	yarn.nodemanager.resource.detect-hardware-capabilities is set to true. The	number of vcores will be calculated as	number of CPUs * multiplier.
	</description>
	<name>yarn.nodemanager.resource.pcores-vcores-multiplier</name>
	<value>1.0</value>
</property>

<property>
	<description>Amount of physical memory, in MB, that can be allocated 
	for containers. If set to -1 and
	yarn.nodemanager.resource.detect-hardware-capabilities is true, it is
	automatically calculated(in case of Windows and Linux).
	In other cases, the default is 8192MB.
	</description>
	<name>yarn.nodemanager.resource.memory-mb</name>
	<value>4096</value>
</property>

<property>
	<description>Number of vcores that can be allocated
	for containers. This is used by the RM scheduler when allocating
	resources for containers. This is not used to limit the number of
	CPUs used by YARN containers. If it is set to -1 and
	yarn.nodemanager.resource.detect-hardware-capabilities is true, it is
	automatically determined from the hardware in case of Windows and Linux.
	In other cases, number of vcores is 8 by default.</description>
	<name>yarn.nodemanager.resource.cpu-vcores</name>
	<value>4</value>
</property>

<property>
	<description>The minimum allocation for every container request at theRM	in MBs. Memory requests lower than this will be set to the value of this	property. Additionally, a node manager that is configured to have less memory	than this value will be shut down by the resource manager.
	</description>
	<name>yarn.scheduler.minimum-allocation-mb</name>
	<value>1024</value>
</property>

<property>
	<description>The maximum allocation for every container request at the RM	in MBs. Memory requests higher than this will throw an	InvalidResourceRequestException.
	</description>
	<name>yarn.scheduler.maximum-allocation-mb</name>
	<value>2048</value>
</property>

<property>
	<description>The minimum allocation for every container request at the RM	in terms of virtual CPU cores. Requests lower than this will be set to the	value of this property. Additionally, a node manager that is configured to	have fewer virtual cores than this value will be shut down by the resource	manager.
	</description>
	<name>yarn.scheduler.minimum-allocation-vcores</name>
	<value>1</value>
</property>

<property>
	<description>The maximum allocation for every container request at the RM	in terms of virtual CPU cores. Requests higher than this will throw an
	InvalidResourceRequestException.</description>
	<name>yarn.scheduler.maximum-allocation-vcores</name>
	<value>2</value>
</property>

<property>
	<description>Whether virtual memory limits will be enforced for
	containers.</description>
	<name>yarn.nodemanager.vmem-check-enabled</name>
	<value>false</value>
</property>

<property>
	<description>Ratio between virtual memory to physical memory when	setting memory limits for containers. Container allocations are	expressed in terms of physical memory, and virtual memory usage	is allowed to exceed this allocation by this ratio.
	</description>
	<name>yarn.nodemanager.vmem-pmem-ratio</name>
	<value>2.1</value>
</property>
```

**关闭虚拟内存检查原因**

![07.Yarn生产环境核心参数配置案例01.jpg](https://lilinchao.com/usr/uploads/2021/09/125297225.jpg)

```xml
<property> 
    <description>Ratio between virtual memory to physical memory when setting memory limits for containers. Container 
    allocations are expressed in terms of physical memory, and virtual memory usage is allowed to exceed this allocation by this ratio. 
    </description> 
    <name>yarn.nodemanager.vmem-pmem-ratio</name> 
    <value>2.1</value> 
</property>
```

#### 1.4 分发配置

*注意：如果集群的硬件资源不一致，要每个NodeManager单独配置*

#### 1.5 重启集群

```
[root@hadoop102 hadoop-3.1.3]# sbin/stop-yarn.sh
[root@hadoop103 hadoop-3.1.3]# sbin/start-yarn.sh
```

#### 1.6 执行WordCount程序

```
[root@hadoop102 hadoop-3.1.3]# hadoop jar 
share/hadoop/mapreduce/hadoop-mapreduce-examples-3.1.3.jar wordcount 
/input /output
```

#### 1.7 观察Yarn任务执行页面

`http://hadoop103:8088/cluster/apps`

*附：*

*文章来源《尚硅谷大数据之Hadoop》*

标签: Hadoop, Yarn

非特殊说明，本博所有文章均为博主原创。

如若转载，请注明出处：https://www.lilinchao.com/archives/1431.html

上一篇 06.Yarn核心参数配置

下一篇 08.Yarn容量调度器多队列配置案例

07.Yarn生产环境核心参数配置案例

评论啦~

栏目分类

标签云

友情链接申请

07.Yarn生产环境核心参数配置案例

 评论啦~

 栏目分类

标签云

友情链接申请

评论啦~

栏目分类

标签云

友情链接申请