@Alex Goron Do you see any discrepancy between the output of the following commands? Can you please share the output? # sudo du -sh /disks/disk1/ # sudo df -h Are you able to make file on your own manually? (this is just to isolate the issue) # echo "ABCDEFGH" > /disks/disk1/log/ambari-metrics-collector/hbase-ams-master-node4.hdp.com.out # echo "ABCDEFGH" > /disks/disk1/log/ambari-metrics-collector/hbase-ams-master-node4.hdp.com.log # echo "ABCDEFGH" > /disks/disk1/log/ambari-metrics-collector/hbase-ams-master-node4.hdp.com.log There might be possibility that the OS still might have some Deleted File Reserved by Processes that we can find out by running the following command. # sudo lsof / | grep deleted If you find some oprocesses aer still holding up "Deleted" files then restart those processes. # sudo systemctl restart $SERVICE_NAME There is a set of metadata on filesystems called “inodes.” Inodes track information about files. # sudo df -i / Also please check if there are any Bad Blocks # sudo fsck -vcck /disks/disk1/ If None of the above helps the Please check if you can reboot the host where AMS is installed. ... View more

@Arif Ishak As we see the error is basically happening because the Port 53 Already Bind 2018-10-23 13:51:37,962 ERROR dns.PrivilegedRegistryDNSStarter (PrivilegedRegistryDNSStarter.java:init(61)) - Error initializing Registry DNS java.net.BindException: Problem binding to [node.b2be.com:53] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException . So please check if your host where you are planning to run the "YARN Registry DNS" has the port 53 available Or some other process is already using that port? # netstat -tnlpa | grep 53 . OR try verifying if you can open the port 53 using simple program like "nc" (netcat) onn that host? Or do you see Already Used port error there as well? # nc -l `hostname -f` 53 Ncat: bind to 10.10.20.30:53: Address already in use. QUITTING. . If yes then Try changing the port to see if it works Or stop the other process which is using that port? Check the value of the following properyy in your YARN configs "hadoop.registry.dns.bind-port". (registry.dns.bind-port) default value = 53 . ... View more

@Ronnie 10 Your JAR name is different. "hadoop-hdfs-client-tests.jar" (wrong jar) and I am using "hadoop-mapreduce-client-jobclient-tests.jar" (correct JAR) Your command: # sudo -u hdfs hadoop jar hadoop-hdfs-client-tests.jar TestDFSIO -write -nrFiles 10 -fileSize 100000 My Command: # cd /usr/hdp/3.0.0.0-1634/hadoop-mapreduce # sudo -u hdfs hadoop jar hadoop-mapreduce-client-jobclient-tests.jar TestDFSIO -write -nrFiles 10 -fileSize 100000 . You can chekc if your JAR contains that class or not ass following: # /usr/jdk64/jdk1.8.0_112/bin/jar -tvf /usr/hdp/3.0.0.0-1634/hadoop-hdfs/hadoop-hdfs-client-tests.jar | grep TestDFSIO Not Found . But if you use the correct JAR then you can see it. # /usr/jdk64/jdk1.8.0_112/bin/jar -tvf /usr/hdp/3.0.0.0-1634/hadoop-mapreduce/hadoop-mapreduce-client-jobclient-tests.jar | grep TestDFSIO 2323 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$ByteMultiple.class 2974 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$ReadMapper.class 4215 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$RandomReadMapper.class 3148 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$TruncateMapper.class 3233 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$WriteMapper.class 4014 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$IOStatMapper.class 1086 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$1.class 24732 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO.class 3078 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$AppendMapper.class 1895 Thu Jul 12 20:36:52 UTC 2018 org/apache/hadoop/fs/TestDFSIO$TestType.class . ... View more