Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 298fecf

Browse files
authoredMay 30, 2022
Update hdinsight-troubleshoot-out-disk-space.md
1 parent 98b8002 commit 298fecf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎articles/hdinsight/hadoop/hdinsight-troubleshoot-out-disk-space.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Apache Yarn application cache may have consumed all available disk space. Your S
2424

2525
1. Use Ambari UI to determine which node is running out of disk space.
2626

27-
1. Determine which folder in the troubling node contributes to most of the disk space. SSH to the node first, then run `df` to list disk usage for all mounts. Usually it's `/mnt`, that is a temp disk used by OSS. You can enter into a folder, then type `sudo du -hs` to show summarized file sizes under a folder. If you see a folder similar to `/mnt/resource/hadoop/yarn/local/usercache/livy/appcache/application_1537280705629_0007`, this output means the application is still running. This output could be due to RDD persistence or intermediate shuffle files.
27+
1. Determine which folder in the troubling node contributes to most of the disk space. SSH to the node first, then run `df` to list disk usage for all mounts. Usually it's `/mnt` that is a temp disk used by OSS. You can enter into a folder, then type `sudo du -hs` to show summarized file sizes under a folder. If you see a folder similar to `/mnt/resource/hadoop/yarn/local/usercache/livy/appcache/application_1537280705629_0007`, this output means the application is still running. This output could be due to RDD persistence or intermediate shuffle files.
2828

2929
1. To mitigate the issue, kill the application, which will release disk space used by that application.
3030

0 commit comments

Comments
 (0)
Please sign in to comment.