如何增加Hadoop中AM可以使用的最大vCores数？

我正在努力进行一些hadoop配置。我正在寻找增加vCore的数量，最大限度地应用程序的主人可以使用

我的问题是目前只能使用1个vCore（见下图），因此我一次只能运行一个作业。其他工作仍将处于接受阶段

我发现了如何增加文件

capacity scheduler.xml

中允许的内存。就我而言：

<configuration>

<property>
<!-- Maximum resources to allocate to application masters
If this is too high application masters can crowd out actual work -->
<name>yarn.scheduler.capacity.maximum-am-resource-percent</name>
<value>0.8</value>
</property>

<property>
<name>yarn.scheduler.capacity.maximum-applications</name>
<value>10000</value>
</property>

<property>
<!-- Yarn knows where the data is local, this is the number of *times*
to try to schedule on a local node before going for rack-local -->
<name>yarn.scheduler.capacity.node-locality-delay</name>
<value>40</value>
</property>

<property>
<!-- This allows users to pick which queue to submit to.
Unless you are genuinely multi-tenant this will make your life easier. -->
<name>yarn.scheduler.capacity.queue-mappings-override.enable</name>
<value>true</value>
</property>

<!-- By default CPUs are ignored for scheduling purposes. 
See https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.0/bk_yarn_resource_mgt/content/ref-7a0a1ca2-72d6-4f3e-82bd-b600e9905acf.1.html -->
<property>
<name>yarn.scheduler.capacity.resource-calculator</name>
<value>org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator</value>
</property>

<!-- Let the root queue access anything -->
<property>
<name>yarn.scheduler.capacity.root.accessible-node-labels</name>
<value>*</value>
</property>

<!-- Root queue can access 100% of data label -->
<property>
<name>yarn.scheduler.capacity.root.accessible-node-labels.data.capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.accessible-node-labels.data.maximum-capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.acl_administer_queue</name>
<value>*</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.accessible-node-labels</name>
<value>*</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.acl_submit_applications</name>
<value>*</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.capacity</name>
<value>98</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.maximum-am-resource-percent</name>
<value>0.75</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.maximum-capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.minimum-user-limit-percent</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.ordering-policy</name>
<value>fair</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.ordering-policy.fair.enable-size-based-weight</name>
<value>false</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.state</name>
<value>RUNNING</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.default.user-limit-factor</name>
<value>35</value>
</property>

<!-- Pin interactive queue to data label -->
<property>
<name>yarn.scheduler.capacity.root.interactive.accessible-node-labels</name>
<value>data</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.accessible-node-labels.data.capacity</name>
<value>20</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.accessible-node-labels.data.maximum-capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.acl_administer_queue</name>
<value>*</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.acl_submit_applications</name>
<value>*</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.capacity</name>
<value>1</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.default-node-label-expression</name>
<value>data</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.maximum-am-resource-percent</name>
<value>0.75</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.maximum-applications</name>
<value>2000</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.maximum-capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.minimum-user-limit-percent</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.state</name>
<value>RUNNING</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.interactive.user-limit-factor</name>
<value>35</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.maximum-capacity</name>
<value>100</value>
</property>

<!-- Pin noninteractive queue to data label -->
<property>
<name>yarn.scheduler.capacity.root.noninteractive.accessible-node-labels</name>
<value>data</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.accessible-node-labels.data.capacity</name>
<value>80</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.accessible-node-labels.data.maximum-capacity</name>
<value>80</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.acl_submit_applications</name>
<value>*</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.capacity</name>
<value>1</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.default-node-label-expression</name>
<value>data</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.maximum-am-resource-percent</name>
<value>0.75</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.maximum-applications</name>
<value>8000</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.maximum-capacity</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.minimum-user-limit-percent</name>
<value>100</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.state</name>
<value>RUNNING</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.noninteractive.user-limit-factor</name>
<value>77</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.queues</name>
<value>default,interactive,noninteractive</value>
</property>

<property>
<name>yarn.scheduler.capacity.root.user-limit-factor</name>
<value>3</value>
</property>

</configuration>

纱线.scheduler.capacity.maximum-am-resource-percent
0.8
纱线.调度器.容量.最大应用
10000
纱线.scheduler.capacity.node-locality-delay
40
warn.scheduler.capacity.queue-mappings-override.enable
符合事实的
纱线.scheduler.capacity.resource-calculator
org.apache.hadoop.warn.util.resource.DefaultResourceCalculator
warn.scheduler.capacity.root.accessible-node-labels
*
纱线.scheduler.capacity.root.accessible-node-labels.data.capacity
100
纱线.scheduler.capacity.root.accessible-node-labels.data.maximum-capacity
100
warn.scheduler.capacity.root.acl\u管理\u队列
*
纱线.scheduler.capacity.root.capacity
100
warn.scheduler.capacity.root.default.accessible-node-labels
*
warn.scheduler.capacity.root.default.acl\u提交\u应用程序
*
warn.scheduler.capacity.root.default.capacity
98
warn.scheduler.capacity.root.default.maximum-am-resource-percent
0.75
warn.scheduler.capacity.root.default.maximum-capacity
100
纱线.scheduler.capacity.root.default.minimum-user-limit-percent
100
warn.scheduler.capacity.root.default.ordering-policy
公平的
纱线.scheduler.capacity.root.default.ordering-policy.fair.enable-size-based-weight
错误的
warn.scheduler.capacity.root.default.state
跑步
warn.scheduler.capacity.root.default.user-limit-factor
35
纱线.scheduler.capacity.root.interactive.accessible-node-labels
数据
纱线.scheduler.capacity.root.interactive.accessible-node-labels.data.capacity
20
纱线.scheduler.capacity.root.interactive.accessible-node-labels.data.maximum-capacity
100
warn.scheduler.capacity.root.interactive.acl\u administrate\u队列
*
warn.scheduler.capacity.root.interactive.acl\u提交应用程序
*
纱线.scheduler.capacity.root.interactive.capacity
1.
warn.scheduler.capacity.root.interactive.default-node-label-expression
数据
纱线.scheduler.capacity.root.interactive.maximum-am-resource-percent
0.75
warn.scheduler.capacity.root.interactive.maximum-applications
2000
纱线.scheduler.capacity.root.interactive.maximum-capacity
100
纱线.scheduler.capacity.root.interactive.minimum-user-limit-percent
100
warn.scheduler.capacity.root.interactive.state
跑步
纱线.scheduler.capacity.root.interactive.user-limit-factor
35
纱线.scheduler.capacity.root.maximum-capacity
100
warn.scheduler.capacity.root.noninteractive.accessible-node-label
数据
纱线.scheduler.capacity.root.noninteractive.accessible-node-labels.data.capacity
80
纱线.scheduler.capacity.root.noninteractive.accessible-node-labels.data.maximum-capacity
80
warn.scheduler.capacity.root.noninteractive.acl\u提交\u应用程序
*
纱线.scheduler.capacity.root.noninteractive.capacity
1.
warn.scheduler.capacity.root.noninteractive.default-node-label-expression
数据
纱线.scheduler.capacity.root.noninteractive.maximum-am-resource-percent
0.75
warn.scheduler.capacity.root.noninteractive.maximum-applications
8000
纱线.scheduler.capacity.root.Non Interactive.maximum-capacity
100
纱线.scheduler.capacity.root.noninteractive.minimum-user-limit-percent
100
warn.scheduler.capacity.root.noninteractive.state
跑步
纱线.scheduler.capacity.root.noninteractive.user-limit-factor
77
warn.scheduler.capacity.root.queues
默认、交互式、非交互式
纱线.scheduler.capacity.root.user-limit-factor
3.

我正在使用Hortonworks 2.6.0
Hadoop版本：Hadoop 2.7.3.2.6.0.3-8

---

提前谢谢。

我想这些就是你要找的

warn.scheduler.minimum allocation vcores

默认值=1
Description=RM上每个容器请求的最小分配，以虚拟CPU核为单位。低于此值的请求将引发InvalidResourceRequestException

warn.scheduler.maximum allocation vcores

默认值=32
Description=RM上每个容器请求的最大分配（以虚拟CPU核为单位）。高于此值的请求将引发InvalidResourceRequestException