Hadoop Yarn性能调优

• Hadoop Yarn性能调优
• • 1 环境
  • 2 yarn-site.xml 配置

版本： hadoop-3.1.3

  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




  Enable auto-detection of node capabilities such a memory and CPU.
  yarn.nodemanager.resource.detect-hardware-capabilities
  false




  Flag to determine if logical processors(such ashyperthreads) 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-ascores
  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
  4096





  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
  4




  The minimum allocation for every container request at the  Hadoop（Yarn） 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
  2048





  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