hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-426) hbase can't find remote filesystem
Date Sat, 09 Feb 2008 01:34:07 GMT

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

stack updated HBASE-426:

    Attachment: rootdir.patch

Change hbase.rootdir to expectation is that its fully-qualified: i.e. includes the filesystem
implementation and full location information.  Addressed also issue Billy Pearson found where
we still referred to hadoop.tmp.dir.  Removed fs.default.name setting in hbase-site.xml for
test.  Tests now use home directory in minidfs as hbase.rootdir. Bulk of the patch is setting
into HBaseConfiguration the rootdir (minidfs randomly picks a port).  Also removed 'default
rootdir'. HBase should fail if you haven't specified root dir for you hbase.

> hbase can't find remote filesystem
> ----------------------------------
>                 Key: HBASE-426
>                 URL: https://issues.apache.org/jira/browse/HBASE-426
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.1.0, 0.2.0
>            Reporter: stack
>            Priority: Blocker
>         Attachments: rootdir.patch
> If filesystem is remote, e.g. its an Hadoop DFS running "over there", there is no means
of pointing hbase at it currently (unless you count copying hadoop-site.xml into hbase/conf).
 Should be possible to just set a fully qualified hbase.rootdir and that should be sufficient
for hbase figuring the fs (needs to be backported to 0.1 too).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message