Hadoop生产调优

头发收割者

于 2023-04-02 00:12:53 发布

阅读量155

点赞数

文章标签： hadoop

本文链接：https://blog.csdn.net/weixin_73641817/article/details/129904721

版权

1.1 NameNode内存生产配置

1)Hadoop2.x系列:NameNode内存默认2000m，如果服务器内存128G，NameNode内存可以配置100g。在hadoop-env.sh文件中配置如下。

HADOOP_NAMENODE_OPTS=-Xmx3072m

2) Hadoop3.x系列: NameNode 内存是动态分配的 .

3) 查看DataNode占用内存

jmap -heap 2744

1.2 NameNode心跳并发配置

1)hdfs-site.xml

<property>

<name>dfs.namenode.handler.count</name>

<value>value</value>

</property>

dfs.namenode.handler.count=20* $\log_{e}clustersize$

1.3 开启回收站配置

1)修改core-site.xml，配置垃圾回收时间为1小时。

<property>

    <name>fs.trash.interval</name>

    <value>60</value>

</property>

2)通过网页上直接删除的文件也不会走回收站,只有在命令行利用hadoop fs -rm命令删除的文件才会走回收站

3)恢复回收站数据

[$user@$host hadoop-3.1.3]$ hadoop fs -mv /user/$host /.Trash/Current/user/$host /input /user/$host /input

1.4 NameNode和DataNode多目录配置

在hdfs-site.xml文件中添加如下内容

<property>

<name>dfs.namenode.name.dir</name>

<value>file://${hadoop.tmp.dir}/dfs/name1,file://${hadoop.tmp.dir}/dfs/name2</value>

</property>

<property>

<name>dfs.datanode.data.dir</name>

<value>file://${hadoop.tmp.dir}/dfs/data1,file://${hadoop.tmp.dir}/dfs/data2</value>

</property>

1.5集群数据均衡之磁盘间数据均衡

1)生产环境，由于硬盘空间不足，往往需要增加一块硬盘。刚加载的硬盘没有数据时，可以执行磁盘数据均衡命令。（Hadoop3.x新特性）

（1）生成均衡计划

hdfs diskbalancer -plan $host

（2）执行均衡计划

hdfs diskbalancer -execute $host.plan.json

（3）查看当前均衡任务的执行情况

hdfs diskbalancer -query $host

（4）取消均衡任务

hdfs diskbalancer -cancel $host.plan.json

1.6集群安全模式&磁盘修复

1）安全模式：文件系统只接受读数据请求，而不接受删除、修改等变更请求

集群处于安全模式，不能执行重要操作（写操作）。集群启动完成后，自动退出安全模式。

（1）bin/hdfs dfsadmin -safemode get （功能描述：查看安全模式状态）

（2）bin/hdfs dfsadmin -safemode enter （功能描述：进入安全模式状态）

（3）bin/hdfs dfsadmin -safemode leave （功能描述：离开安全模式状态）

（4）bin/hdfs dfsadmin -safemode wait （功能描述：等待安全模式状态）

2)磁盘修复

观察http://$host:9870/dfshealth.html#tab-overview

将元数据删除

1.7HDFS—集群迁移

1）scp实现两个远程主机之间的文件复制

scp -r hello.txt root@$host:/user/hello.txt // 推 push

scp -r root@$host :/user/hello.txt hello.txt // 拉 pull

scp -r root@$host:/user/hello.txt root@$host:/user/ //是通过本地主机中转实现两个远程主机的文件复制；如果在两个远程主机之间ssh没有配置的情况下可以使用该方式。

2）采用distcp命令实现两个Hadoop集群之间的递归数据复制

[user@$host hadoop-3.1.3]$ bin/hadoop distcp hdfs://$host:8020/user/hello.txt hdfs://$host:8020/user/hello.txt

1.8 MapReduce数据倾斜问题

数据频率倾斜——某一个区域的数据量要远远大于其他区域。

数据大小倾斜——部分记录的大小远远大于平均值。

（1）首先检查是否空值过多造成的数据倾斜生产环境，可以直接过滤掉空值；如果想保留空值，就自定义分区，将空值加随机数打散。最后再二次聚合。

（2）能在map阶段提前处理，最好先在Map阶段处理。如：Combiner、MapJoin

（3）设置多个reduce个数

2调优案例

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

（2）需求分析：

1G / 128m = 8个MapTask；1个ReduceTask；1个mrAppMaster

平均每个节点运行10个 / 3台 ≈ 3个任务（4 3 3）

HDFS参数调优

（1）修改：hadoop-env.sh

export HDFS_NAMENODE_OPTS="-Dhadoop.security.logger=INFO,RFAS -Xmx1024m"

export HDFS_DATANODE_OPTS="-Dhadoop.security.logger=ERROR,RFAS -Xmx1024m"

（2）修改hdfs-site.xml

<property>

<name>dfs.namenode.handler.count</name>

<value>21</value>

</property>

（3）修改core-site.xml

<property>

<name>fs.trash.interval</name>

<value>60</value>

</property>

（4）分发配置

xsync hadoop-env.sh hdfs-site.xml core-site.xml

10.3.3 MapReduce参数调优

（1）修改mapred-site.xml

<property>

<name>mapreduce.task.io.sort.mb</name>

<value>100</value>

</property>

<property>

<name>mapreduce.map.sort.spill.percent</name>

<value>0.80</value>

</property>

<property>

<name>mapreduce.task.io.sort.factor</name>

<value>10</value>

</property>

<property>

  <name>mapreduce.map.memory.mb</name>

  <value>-1</value>

  <description>The amount of memory to request from the scheduler for each    map task. If this is not specified or is non-positive, it is inferred from mapreduce.map.java.opts and mapreduce.job.heap.memory-mb.ratio. If java-opts are also not specified, we set it to 1024.

  </description>

</property>

<property>

<name>mapreduce.map.cpu.vcores</name>

<value>1</value>

</property>

<property>

<name>mapreduce.map.maxattempts</name>

<value>4</value>

</property>

<property>

<name>mapreduce.reduce.shuffle.parallelcopies</name>

<value>5</value>

</property>

<property>

<name>mapreduce.reduce.shuffle.input.buffer.percent</name>

<value>0.70</value>

</property>

<property>

<name>mapreduce.reduce.shuffle.merge.percent</name>

<value>0.66</value>

</property>

<property>

  <name>mapreduce.reduce.memory.mb</name>

  <value>-1</value>

  <description>The amount of memory to request from the scheduler for each    reduce task. If this is not specified or is non-positive, it is inferred

    from mapreduce.reduce.java.opts and mapreduce.job.heap.memory-mb.ratio.

<property>

<name>mapreduce.reduce.cpu.vcores</name>

<value>2</value>

</property>

<property>

<name>mapreduce.reduce.maxattempts</name>

<value>4</value>

</property>

<property>

<name>mapreduce.job.reduce.slowstart.completedmaps</name>

<value>0.05</value>

</property>

<property>

<name>mapreduce.task.timeout</name>

<value>600000</value>

</property>

（2）分发配置

xsync mapred-site.xml

Yarn参数调优

（1）修改yarn-site.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 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.

</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>