HA配置之yarnsite.xml

yarn.nodemanager.aux-services
mapreduce_shuffle

yarn.resourcemanager.ha.enabled
true

yarn.resourcemanager.cluster-id
cluster-yarn1

yarn.resourcemanager.ha.rm-ids
rm1,rm2

yarn.resourcemanager.hostname.rm1
hadoop102

yarn.resourcemanager.webapp.address.rm1
hadoop102:8088

yarn.resourcemanager.address.rm1
hadoop102:8032

yarn.resourcemanager.scheduler.address.rm1
hadoop102:8030

yarn.resourcemanager.resource-tracker.address.rm1
hadoop102:8031

yarn.resourcemanager.hostname.rm2
hadoop105

yarn.resourcemanager.webapp.address.rm2
hadoop105:8088

yarn.resourcemanager.address.rm2
hadoop105:8032

yarn.resourcemanager.scheduler.address.rm2
hadoop105:8030

yarn.resourcemanager.resource-tracker.address.rm2
hadoop105:8031

yarn.resourcemanager.zk-address
hadoop102:2181,hadoop105:2181,hadoop106:2181

yarn.resourcemanager.recovery.enabled
true

yarn.resourcemanager.store.class org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore

yarn.nodemanager.env-whitelist
JAVA_HOME,HADOOP_COMMON_HOME,HADOOP_HDFS_HOME,HADOOP_CONF_DIR,CLASSPATH_PREPEND_DISTCACHE,HADOOP_YARN_HOME,HADOOP_MAPRED_HOME

The class to use as the resource scheduler.
yarn.resourcemanager.scheduler.class
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler

Number of threads to handle scheduler interface.
yarn.resourcemanager.scheduler.client.thread-count
8

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.

yarn.nodemanager.resource.count-logical-processors-as-cores
false

Enable auto-detection of node capabilities such as
memory and CPU.

yarn.nodemanager.resource.detect-hardware-capabilities
false

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.

yarn.nodemanager.resource.pcores-vcores-multiplier
1.0

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.

yarn.nodemanager.resource.memory-mb
6144

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.
yarn.nodemanager.resource.cpu-vcores
2

The minimum allocation for every container request at the RM 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.

yarn.scheduler.minimum-allocation-mb
1024

The maximum allocation for every container request at the RM in MBs. Memory requests higher than this will throw an InvalidResourceRequestException.

yarn.scheduler.maximum-allocation-mb
6144

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.

yarn.scheduler.minimum-allocation-vcores
1

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

Whether virtual memory limits will be enforced for
containers.
yarn.nodemanager.vmem-check-enabled
false

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.

yarn.nodemanager.vmem-pmem-ratio
2.1

yarn.log-aggregation-enable
true

yarn.log.server.url
http://hadoop102:19888/jobhistory/logs

yarn.log-aggregation.retain-seconds
604800