You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Rong-En Fan (JIRA)" <ji...@apache.org> on 2008/04/11 06:34:04 UTC

[jira] Created: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib
--------------------------------------------------------------------------------------

                 Key: HBASE-573
                 URL: https://issues.apache.org/jira/browse/HBASE-573
             Project: Hadoop HBase
          Issue Type: Bug
    Affects Versions: 0.1.0
            Reporter: Rong-En Fan
            Priority: Blocker


When HBase was in hadoop/contrib, the hbase script set both HADOOP_CONF_DIR
and HBASE_CONF_DIR to CLASSPATH, so that dfs's configuration can be loaded
correctly. However, when moved out hadoop/contrib, it only sets HBASE_CONF_DIR.

I can think of several possible solutions:

1) set HADOOP_CONF_DIR in hbase-env.sh, then add HADOOP_CONF_DIR to CLASSPATH as before
2) Instruct user to create links for hadoop-*.xml if they want to customize some dfs settings.
3) If only a small set of dfs confs are related to dfs's client, maybe they can be set via  hbase-site.xml, then hbase sets these for us when create a FileSystem obj.

Please see the thread "# of dfs replications when using hbase" on hbase-user@.



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


Re: [jira] Updated: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by stack <st...@duboce.net>.
Yes.
St.Ack


R. James Firby wrote:
> Yes, I guess that would work.  We actually split our hadoop configs into two directories, one for the dfs and one for map/reduce so we can run multiple map/reduce clusters on the same set of machines that are all running the dfs.
>
> So, we could just set HADOOP_CONF_DIR in hbase-env.sh to point to the dfs config directory and all would be well.  Right?
>
> Jim
>
>
> On 4/11/08 1:43 PM, "stack" <st...@duboce.net> wrote:
>
> R. James Firby wrote:
>   
>> Let's be careful with this one.
>>
>> We run hadoop with non-default configs that live in a different directory from where hbase and its configs are installed.   For us, a really nice thing would be to have a value we can set in the hbase config that would point to the proper hadoop config to use.
>>
>>     
>
> Does adding wherever HADOOP_CONF_DIR points to the HBASE_CLASSPATH in
> hbase-env.sh work for you Jim?   Or would you like something else?
> Thanks,
> St.Ack
>
>
>
>   


Re: [jira] Updated: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by "R. James Firby" <fi...@powerset.com>.
Yes, I guess that would work.  We actually split our hadoop configs into two directories, one for the dfs and one for map/reduce so we can run multiple map/reduce clusters on the same set of machines that are all running the dfs.

So, we could just set HADOOP_CONF_DIR in hbase-env.sh to point to the dfs config directory and all would be well.  Right?

Jim


On 4/11/08 1:43 PM, "stack" <st...@duboce.net> wrote:

R. James Firby wrote:
> Let's be careful with this one.
>
> We run hadoop with non-default configs that live in a different directory from where hbase and its configs are installed.   For us, a really nice thing would be to have a value we can set in the hbase config that would point to the proper hadoop config to use.
>

Does adding wherever HADOOP_CONF_DIR points to the HBASE_CLASSPATH in
hbase-env.sh work for you Jim?   Or would you like something else?
Thanks,
St.Ack



Re: [jira] Updated: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by stack <st...@duboce.net>.
R. James Firby wrote:
> Let's be careful with this one.
>
> We run hadoop with non-default configs that live in a different directory from where hbase and its configs are installed.   For us, a really nice thing would be to have a value we can set in the hbase config that would point to the proper hadoop config to use.
>   

Does adding wherever HADOOP_CONF_DIR points to the HBASE_CLASSPATH in 
hbase-env.sh work for you Jim?   Or would you like something else?
Thanks,
St.Ack

Re: [jira] Updated: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by "R. James Firby" <fi...@powerset.com>.
Let's be careful with this one.

We run hadoop with non-default configs that live in a different directory from where hbase and its configs are installed.   For us, a really nice thing would be to have a value we can set in the hbase config that would point to the proper hadoop config to use.

Slurping up whatever hadoop config happens to be on the classpath may not be correct and will definitely add confusion to the config process.

Jim

[jira] Updated: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-573:
------------------------

    Fix Version/s: 0.1.2
                   0.2.0

Lets address in 0.1.2 (as well as TRUNK)

> HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-573
>                 URL: https://issues.apache.org/jira/browse/HBASE-573
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0, 0.1.2, 0.1.1, 0.1.0
>            Reporter: Rong-En Fan
>            Priority: Blocker
>             Fix For: 0.2.0, 0.1.2
>
>
> When HBase was in hadoop/contrib, the hbase script set both HADOOP_CONF_DIR
> and HBASE_CONF_DIR to CLASSPATH, so that dfs's configuration can be loaded
> correctly. However, when moved out hadoop/contrib, it only sets HBASE_CONF_DIR.
> I can think of several possible solutions:
> 1) set HADOOP_CONF_DIR in hbase-env.sh, then add HADOOP_CONF_DIR to CLASSPATH as before
> 2) Instruct user to create links for hadoop-*.xml if they want to customize some dfs settings.
> 3) If only a small set of dfs confs are related to dfs's client, maybe they can be set via  hbase-site.xml, then hbase sets these for us when create a FileSystem obj.
> Please see the thread "# of dfs replications when using hbase" on hbase-user@.

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


[jira] Resolved: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-573.
-------------------------

    Resolution: Fixed

Committed doc. to branch, trunk and to FAQ.

> HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-573
>                 URL: https://issues.apache.org/jira/browse/HBASE-573
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0, 0.1.2, 0.1.0, 0.1.1
>            Reporter: Rong-En Fan
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.2.0, 0.1.2
>
>
> When HBase was in hadoop/contrib, the hbase script set both HADOOP_CONF_DIR
> and HBASE_CONF_DIR to CLASSPATH, so that dfs's configuration can be loaded
> correctly. However, when moved out hadoop/contrib, it only sets HBASE_CONF_DIR.
> I can think of several possible solutions:
> 1) set HADOOP_CONF_DIR in hbase-env.sh, then add HADOOP_CONF_DIR to CLASSPATH as before
> 2) Instruct user to create links for hadoop-*.xml if they want to customize some dfs settings.
> 3) If only a small set of dfs confs are related to dfs's client, maybe they can be set via  hbase-site.xml, then hbase sets these for us when create a FileSystem obj.
> Please see the thread "# of dfs replications when using hbase" on hbase-user@.

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


[jira] Assigned: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reassigned HBASE-573:
---------------------------

    Assignee: stack

> HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-573
>                 URL: https://issues.apache.org/jira/browse/HBASE-573
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0, 0.1.2, 0.1.1, 0.1.0
>            Reporter: Rong-En Fan
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.2.0, 0.1.2
>
>
> When HBase was in hadoop/contrib, the hbase script set both HADOOP_CONF_DIR
> and HBASE_CONF_DIR to CLASSPATH, so that dfs's configuration can be loaded
> correctly. However, when moved out hadoop/contrib, it only sets HBASE_CONF_DIR.
> I can think of several possible solutions:
> 1) set HADOOP_CONF_DIR in hbase-env.sh, then add HADOOP_CONF_DIR to CLASSPATH as before
> 2) Instruct user to create links for hadoop-*.xml if they want to customize some dfs settings.
> 3) If only a small set of dfs confs are related to dfs's client, maybe they can be set via  hbase-site.xml, then hbase sets these for us when create a FileSystem obj.
> Please see the thread "# of dfs replications when using hbase" on hbase-user@.

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


[jira] Updated: (HBASE-573) HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib

Posted by "Rong-En Fan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rong-En Fan updated HBASE-573:
------------------------------

    Affects Version/s: 0.1.1
                       0.1.2
                       0.2.0

> HBase does not read hadoop-*.xml for dfs configuration after moving out hadoop/contrib
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-573
>                 URL: https://issues.apache.org/jira/browse/HBASE-573
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0, 0.1.2, 0.1.1, 0.1.0
>            Reporter: Rong-En Fan
>            Priority: Blocker
>
> When HBase was in hadoop/contrib, the hbase script set both HADOOP_CONF_DIR
> and HBASE_CONF_DIR to CLASSPATH, so that dfs's configuration can be loaded
> correctly. However, when moved out hadoop/contrib, it only sets HBASE_CONF_DIR.
> I can think of several possible solutions:
> 1) set HADOOP_CONF_DIR in hbase-env.sh, then add HADOOP_CONF_DIR to CLASSPATH as before
> 2) Instruct user to create links for hadoop-*.xml if they want to customize some dfs settings.
> 3) If only a small set of dfs confs are related to dfs's client, maybe they can be set via  hbase-site.xml, then hbase sets these for us when create a FileSystem obj.
> Please see the thread "# of dfs replications when using hbase" on hbase-user@.

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