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

Hadoop QA commented on HBASE-6067:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12530821/6067-addendum.txt
  against trunk revision .

    +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 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2100//console

This message is automatically generated.
                
> HBase won't start when hbase.rootdir uses ViewFileSystem
> --------------------------------------------------------
>
>                 Key: HBASE-6067
>                 URL: https://issues.apache.org/jira/browse/HBASE-6067
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Eli Collins
>            Assignee: Zhihong Ted Yu
>             Fix For: 0.96.0, 0.94.1, 0.92.3
>
>         Attachments: 6067-addendum.txt, 6067-v2.txt, 6067.txt
>
>
> HBase currently doesn't work with HDFS federation (hbase.rootdir with a 
> client that uses viewfs) because HLog#init uses 
> FileSystem#getDefaultBlockSize and getDefaultReplication. These throw an 
> exception because there is no default filesystem in a viewfs client so 
> there's no way to determine a default block size or replication factor. They 
> could use the versions of these methods that take a path, however these were 
> introduced in HADOOP-8014 and are not yet available in Hadoop 1.x.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to