[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2964:
--
Status: Open (was: Patch Available)
> No notice in any logs if dfs.datanode.du.reserved is greater than availabl
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2964:
--
Attachment: HDFS-2964-3.patch
> No notice in any logs if dfs.datanode.du.reserved is greater than available
> di
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2964:
--
Component/s: (was: namenode)
> No notice in any logs if dfs.datanode.du.reserved is greater than available
>
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2964:
--
Affects Version/s: (was: 0.20.2)
2.6.0
> No notice in any logs if dfs.datanode.du.rese
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2964:
--
Attachment: HDFS-2964-2.patch
+1 on this. I cleaned up the message to be more informative (print path and
bytes
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
madhukara phatak updated HDFS-2964:
---
Status: Patch Available (was: Open)
> No notice in any logs if dfs.datanode.du.reserved i
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
madhukara phatak updated HDFS-2964:
---
Attachment: HDFS-2964-1.patch
Fixed the patch file to have only changed code and converted new
[
https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
madhukara phatak updated HDFS-2964:
---
Attachment: HDFS-2964.patch
Added a warning message in FsVolumeImpl.java where it reads the la
