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

Hadoop QA commented on HBASE-8304:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12630630/HBASE-8304.patch
  against trunk revision .
  ATTACHMENT ID: 12630630

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  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.

    {color:red}-1 hadoop1.0{color}.  The patch failed to compile against the 
hadoop 1.0 profile.
    Here is snippet of errors:
    {code}[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project hbase-server: Compilation failure
[ERROR] 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java:[430,70]
 cannot find symbol
[ERROR] symbol  : method 
getNNServiceRpcAddresses(org.apache.hadoop.conf.Configuration)
[ERROR] location: class org.apache.hadoop.hdfs.DFSUtil
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project hbase-server: Compilation failure
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java:[430,70]
 cannot find symbol
symbol  : method getNNServiceRpcAddresses(org.apache.hadoop.conf.Configuration)
location: class org.apache.hadoop.hdfs.DFSUtil

        at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
--
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation 
failure
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java:[430,70]
 cannot find symbol
symbol  : method getNNServiceRpcAddresses(org.apache.hadoop.conf.Configuration)
location: class org.apache.hadoop.hdfs.DFSUtil

        at 
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:729){code}

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

This message is automatically generated.

> Bulkload fail to remove files if fs.default.name / fs.defaultFS is configured 
> without default port.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8304
>                 URL: https://issues.apache.org/jira/browse/HBASE-8304
>             Project: HBase
>          Issue Type: Bug
>          Components: HFile, regionserver
>    Affects Versions: 0.94.5
>            Reporter: Raymond Liu
>              Labels: bulkloader
>         Attachments: HBASE-8304.patch
>
>
> When fs.default.name or fs.defaultFS in hadoop core-site.xml is configured as 
> hdfs://ip, and hbase.rootdir is configured as hdfs://ip:port/hbaserootdir 
> where port is the hdfs namenode's default port. the bulkload operation will 
> not remove the file in bulk output dir. Store::bulkLoadHfile will think 
> hdfs:://ip and hdfs:://ip:port as different filesystem and go with copy 
> approaching instead of rename.
> The root cause is that hbase master will rewrite fs.default.name/fs.defaultFS 
> according to hbase.rootdir when regionserver started, thus, dest fs uri from 
> the hregion will not matching src fs uri passed from client.
> any suggestion what is the best approaching to fix this issue? 
> I kind of think that we could check for default port if src uri come without 
> port info.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to