Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 343D010B04 for ; Wed, 5 Mar 2014 14:45:47 +0000 (UTC) Received: (qmail 39639 invoked by uid 500); 5 Mar 2014 14:45:46 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 39599 invoked by uid 500); 5 Mar 2014 14:45:45 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 39578 invoked by uid 99); 5 Mar 2014 14:45:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2014 14:45:44 +0000 Date: Wed, 5 Mar 2014 14:45:44 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10677) boundaries check in hbck throwing IllegalArgumentException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920898#comment-13920898 ] Hadoop QA commented on HBASE-10677: ----------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12632814/HBASE-10677_v2.patch against trunk revision . ATTACHMENT ID: 12632814 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified tests. {color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile. {color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop 1.1 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8901//console This message is automatically generated. > boundaries check in hbck throwing IllegalArgumentException > ---------------------------------------------------------- > > Key: HBASE-10677 > URL: https://issues.apache.org/jira/browse/HBASE-10677 > Project: HBase > Issue Type: Bug > Components: hbck > Affects Versions: 0.98.0 > Reporter: rajeshbabu > Assignee: rajeshbabu > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10677.patch, HBASE-10677_v1.patch, HBASE-10677_v2.patch > > > This is the exception > {code} > java.lang.IllegalArgumentException: Pathname /hbase/hbase:labels/438f84dea5d0e24e390de927deb8a84e from hdfs://10.18.40.29:54310/hbase/hbase:labels/438f84dea5d0e24e390de927deb8a84e is not a valid DFS filename. > at org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:184) > at org.apache.hadoop.hdfs.DistributedFileSystem.listStatusInternal(DistributedFileSystem.java:637) > at org.apache.hadoop.hdfs.DistributedFileSystem.access$600(DistributedFileSystem.java:92) > at org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:702) > at org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:698) > at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) > at org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:698) > at org.apache.hadoop.hbase.util.HBaseFsck.checkRegionBoundaries(HBaseFsck.java:537) > at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:487) > at org.apache.hadoop.hbase.util.HBaseFsck.exec(HBaseFsck.java:4028) > at org.apache.hadoop.hbase.util.HBaseFsck$HBaseFsckTool.run(HBaseFsck.java:3837) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3825) > {code} > We are pointing to wrong table directory. This is the code causing the problem. > {code} > // For each region, get the start and stop key from the META and compare them to the > // same information from the Stores. > Path path = new Path(getConf().get(HConstants.HBASE_DIR) + "/" > + Bytes.toString(regionInfo.getTable().getName()) + "/" > + regionInfo.getEncodedName() + "/"); > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)