hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-7048) Regionsplitter requires the hadoop config path to be in hbase classpath
Date Thu, 25 Oct 2012 16:07:12 GMT

     [ https://issues.apache.org/jira/browse/HBASE-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Yu updated HBASE-7048:
--------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Integrated to 0.94 and trunk.

Thanks for the patch, Ming.

Thanks for the review, Ram and Lars.
                
> Regionsplitter requires the hadoop config path to be in hbase classpath
> -----------------------------------------------------------------------
>
>                 Key: HBASE-7048
>                 URL: https://issues.apache.org/jira/browse/HBASE-7048
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.2
>            Reporter: Ted Yu
>             Fix For: 0.94.3, 0.96.0
>
>         Attachments: 7048-0.94.patch, 7048-trunk.patch
>
>
> When hadoop config path isn't included in hbase classpath, you will get the following:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: Wrong FS: hdfs://t3.e.com/hbase/usertable/_balancedSplit,
expected: file:///
> at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:454)
> at org.apache.hadoop.fs.RawLocalFileSystem.pathToFile(RawLocalFileSystem.java:67)
> at org.apache.hadoop.fs.RawLocalFileSystem.getFileStatus(RawLocalFileSystem.java:431)
> at org.apache.hadoop.fs.FilterFileSystem.getFileStatus(FilterFileSystem.java:301)
> at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1005)
> at org.apache.hadoop.hbase.util.RegionSplitter.getSplits(RegionSplitter.java:643)
> at org.apache.hadoop.hbase.util.RegionSplitter.rollingSplit(RegionSplitter.java:367)
> at org.apache.hadoop.hbase.util.RegionSplitter.main(RegionSplitter.java:295)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message