hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13717) TestBoundedRegionGroupingProvider#setMembershipDedups need to set HDFS diretory for WAL
Date Wed, 20 May 2015 04:56:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551810#comment-14551810
] 

Hudson commented on HBASE-13717:
--------------------------------

FAILURE: Integrated in HBase-1.0 #920 (See [https://builds.apache.org/job/HBase-1.0/920/])
HBASE-13717 TestBoundedRegionGroupingProvider#setMembershipDedups need to set HDFS diretory
for WAL (Stephen Yuan Jiang) (enis: rev 10b4278609a93e14ae4491ddc626ab4b2b8c801a)
* hbase-server/src/test/java/org/apache/hadoop/hbase/wal/TestBoundedRegionGroupingProvider.java


> TestBoundedRegionGroupingProvider#setMembershipDedups need to set HDFS diretory for WAL
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-13717
>                 URL: https://issues.apache.org/jira/browse/HBASE-13717
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>    Affects Versions: 2.0.0, 1.1.0, 1.2.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>            Priority: Minor
>             Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.1
>
>         Attachments: HBASE-13717.patch
>
>
> org.apache.hadoop.hbase.wal.TestBoundedRegionGroupingProvider#setMembershipDedups() fails
during testing in windows:
> {noformat}
> java.lang.IllegalArgumentException: Pathname /C:/tmp/hbase-myuser/hbase/WALs/setMembershipDedups
from hdfs://127.0.0.1:61737/C:/tmp/hbase-myuser/hbase/WALs/setMembershipDedups is not a valid
DFS filename.
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:197)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.access$000(DistributedFileSystem.java:106)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1305)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1301)
> 	at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> 	at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1301)
> 	at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1424)
> 	at org.apache.hadoop.hbase.regionserver.wal.FSHLog.<init>(FSHLog.java:477)
> 	at org.apache.hadoop.hbase.wal.DefaultWALProvider.init(DefaultWALProvider.java:97)
> 	at org.apache.hadoop.hbase.wal.WALFactory.getProvider(WALFactory.java:147)
> 	at org.apache.hadoop.hbase.wal.BoundedRegionGroupingProvider.init(BoundedRegionGroupingProvider.java:56)
> 	at org.apache.hadoop.hbase.wal.WALFactory.getProvider(WALFactory.java:147)
> 	at org.apache.hadoop.hbase.wal.WALFactory.<init>(WALFactory.java:179)
> 	at org.apache.hadoop.hbase.wal.TestBoundedRegionGroupingProvider.setMembershipDedups(TestBoundedRegionGroupingProvider.java:161)
> {noformat}
> This is due to using the local file system path as root directory.  We should set the
HDFS directory as the root directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message