[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13051049#comment-13051049 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-trunk #699 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/699/]) Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch, branch-0.22-hdfs-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050132#comment-13050132 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/746/]) Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch, branch-0.22-hdfs-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13048300#comment-13048300 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-22-branch #66 (See [https://builds.apache.org/job/Hadoop-Hdfs-22-branch/66/]) Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch, branch-0.22-hdfs-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047434#comment-13047434 ] Patrick Hunt commented on HDFS-1954: Thanks Konstantin! Also, really appreciate the f/b you all provided and your patience. I originally picked this up thinking it would be a simple slam dunk change for me to cut my teeth on. :-) Regards. Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch, branch-0.22-hdfs-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13045636#comment-13045636 ] Hadoop QA commented on HDFS-1954: - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12481740/HDFS-1954.patch against trunk revision 1133114. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these core unit tests: org.apache.hadoop.cli.TestHDFSCLI +1 contrib tests. The patch passed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/735//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/735//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/735//console This message is automatically generated. Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13045657#comment-13045657 ] Patrick Hunt commented on HDFS-1954: TestHDFSCLI is currently broken in trunk, not caused by this patch: https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Hdfs-trunk/690/testReport/junit/org.apache.hadoop.cli/TestHDFSCLI/ also TestMissingBlocksAlert is covering this change. Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13044795#comment-13044795 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-22-branch #61 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-22-branch/61/]) Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13045060#comment-13045060 ] Konstantin Shvachko commented on HDFS-1954: --- FAQ is here: [HDFS 3.15|http://wiki.apache.org/hadoop/FAQ#I_got_a_warning_on_the_NameNode_web_UI_.22WARNING_:_There_are_about_32_missing_blocks._Please_check_the_log_or_run_fsck..22_What_does_it_mean.3F]. Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043326#comment-13043326 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-trunk #686 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/686/]) Revert HDFS-1954 since there is some discussion on the JIRA. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1130693 Files : * /hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/namenode/NamenodeJspHelper.java * /hadoop/hdfs/trunk/src/webapps/hdfs/dfshealth.jsp * /hadoop/hdfs/trunk/CHANGES.txt Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042944#comment-13042944 ] Tsz Wo (Nicholas), SZE commented on HDFS-1954: -- Revised the title. Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042948#comment-13042948 ] Patrick Hunt commented on HDFS-1954: Yea that's on me, sorry. It's weird -- the patch test indicated success. I'll update the patch, incl the test, once Konstantin updates the FAQ. Thanks Suresh/Todd. Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042954#comment-13042954 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-trunk-Commit #705 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/705/]) Revert HDFS-1954 since there is some discussion on the JIRA. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1130693 Files : * /hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/namenode/NamenodeJspHelper.java * /hadoop/hdfs/trunk/src/webapps/hdfs/dfshealth.jsp * /hadoop/hdfs/trunk/CHANGES.txt Improve corrupt files warning message on NameNode web UI Key: HDFS-1954 URL: https://issues.apache.org/jira/browse/HDFS-1954 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: philo vivero Assignee: Patrick Hunt Fix For: 0.22.0 Attachments: HDFS-1954.patch, HDFS-1954.patch Original Estimate: 24h Remaining Estimate: 24h On NameNode web interface, you may get this warning: WARNING : There are about 32 missing blocks. Please check the log or run fsck. If the cluster was started less than 14 days before, it would be great to add: Is dfs.data.dir defined? If at the point of that error message, that parameter could be checked, and error made OMG dfs.data.dir isn't defined! that'd be even better. As is, troubleshooting undefined parameters is a difficult proposition. I suspect this is an easy fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
