Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.3.6
-
None
-
None
Description
My hadoop version is 3.3.6, and I use the Pseudo-Distributed Operation.
If yarn.nodemanager.resource.memory-mb and mapreduce.map.memory.mb violate the relationship, it will cause the mapreduce sample program to block.
The first configuraion should be larger than the second one, but we manually violate the relationship.
Here we provide the entire process.
core-site.xml like below.
<configuration>
<property>
<name>fs.defaultFS</name>
<value>hdfs://localhost:9000</value>
</property>
<property>
<name>hadoop.tmp.dir</name>
<value>/home/lfl/Mutil_Component/tmp</value>
</property>
</configuration>
hdfs-site.xml like below.
<configuration> <property> <name>dfs.replication</name> <value>1</value> </property> </configuration>
And then format the namenode, and start the hdfs. HDFS is running normally.
lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$ ./bin/hdfs namenode -format lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$ ./sbin/start-dfs.sh
We add yarn.nodemanager.resource.memory-mb to yarn-site.xml like below.
<property>
<name>yarn.nodemanager.resource.memory-mb</name>
<value>1024</value>
</property>
Also, we alse add mapreduce.map.memory.mb to mapred-site.xml like below.
<property>
<name>mapreduce.map.memory.mb</name>
<value>2048</value>
</property>
Finally, we start the yarn and run the given mapreduce sample job.
lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$ bin/hdfs dfs -mkdir -p /user/lfl
lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$ bin/hdfs dfs -mkdir input
lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$ bin/hdfs dfs -put etc/hadoop/*.xml input
lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$ sbin/start-yarn.sh
Starting resourcemanager
Starting nodemanagers
lfl@LAPTOP-QR7GJ7B1:~/Mutil_Component/hadoop-3.3.6$bin/hadoop jar share/hadoop/mapreduce/hadoop-mapreduce-examples-3.3.6.jar grep input output 'dfs[a-z.]+'
2023-10-26 10:44:47,027 INFO client.DefaultNoHARMFailoverProxyProvider: Connecting to ResourceManager at localhost/127.0.0.1:8032 2023-10-26 10:44:47,288 INFO mapreduce.JobResourceUploader: Disabling Erasure Coding for path: /tmp/hadoop-yarn/staging/lfl/.staging/job_1698288283355_0001 2023-10-26 10:44:47,483 INFO input.FileInputFormat: Total input files to process : 10 2023-10-26 10:44:47,930 INFO mapreduce.JobSubmitter: number of splits:10 2023-10-26 10:44:48,406 INFO mapreduce.JobSubmitter: Submitting tokens for job: job_1698288283355_0001 2023-10-26 10:44:48,406 INFO mapreduce.JobSubmitter: Executing with tokens: [] 2023-10-26 10:44:48,513 INFO conf.Configuration: resource-types.xml not found 2023-10-26 10:44:48,513 INFO resource.ResourceUtils: Unable to find 'resource-types.xml'. 2023-10-26 10:44:48,669 INFO impl.YarnClientImpl: Submitted application application_1698288283355_0001 2023-10-26 10:44:48,703 INFO mapreduce.Job: The url to track the job: http://LAPTOP-QR7GJ7B1.localdomain:8088/proxy/application_1698288283355_0001/ 2023-10-26 10:44:48,703 INFO mapreduce.Job: Running job: job_1698288283355_0001
And, it will continue to be blocked here.
Additionally, the following two types of configuration dependency violations can also cause the same problem.
dependency：yarn.nodemanager.resource.memory-mb>=yarn.app.mapreduce.am.resource.mb yarn-site.xml <property> <name>yarn.nodemanager.resource.memory-mb</name> <value>1024</value> </property> mapred-site.xml <property> <name>yarn.app.mapreduce.am.resource.mb</name> <value>2048</value> </property>
dependeny：yarn.nodemanager.resource.memory-mb>=mapreduce.reduce.memory.mb yarn-site.xml <property> <name>yarn.nodemanager.resource.memory-mb</name> <value>1024</value> </property> mapred-site.xml <property> <name>mapreduce.reduce.memory.mb</name> <value>2048</value> </property>