My Yarn version is 3.3.4, and I tested it on CentOS using Yarn SLS (Schedule Load Simulator). I found that no relevant exceptions were found during runtime, and real-time tracking. json, jobruntime. csv, tableMapping. csv, and metrics related data were generated. I access port 10001, which is the w
Hello.I have a version 3.3.4 Hadoop cluster with over a thousand datanodes. I want to use HDFS Router based Federation. May I ask you a few questions.The first question is, is it better to deploy the router on the namenode server or separately? I want to add a set of Namenodes to the existing HDFS
Hello, please help me take a look at this issue. Due to openssl, Hadoop compilation failed. When I try to compile Hadoop, I add -Drequire.openssl to the maven command, and the Hadoop compilation will fail. I encountered this issue when compiling in the x86 environment, and I successfully compiled
Hi,A 1-replica HDFS cluster with a single DataNode. When the DataNode was restarted after power failure, it found a file with a missing block. The size of the block and mate files found in the storage path is empty, and the last modification time is the power off time. Besides the fact that the fil
hello HDFS cluster version 2.7.2, I set a space quota for the directory, but the available space is much less than expected, for example, this image has a quota of 600T, 31T used space, it should be 500T free space, but it actually shows only 132T. I randomly checked the number of file copies in th
ed in 2017. It's missing numerous bug fixes and security patches. I recommend looking into an upgrade to 2.10.2 in the short term, followed by a plan for getting onto a currently supported 3.x release. I hope this helps.Chris Nauroth On Mon, Oct 24, 2022 at 11:31 PM hehaore...@gmail.com <he
I have an HDFS cluster, version 2.7.2, with two namenodes and three datanodes. While uploads the file, an exception is found: java.io.IOException: Got error,status message,ack with firstBadLink as X:50010. I noticed that the datanode log is stopped, only datanode.log.1, not datanode.log. But the re
