You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/07/01 00:42:47 UTC

[jira] Resolved: (HBASE-1595) hadoop-default.xml and zoo.cfg in hbase jar

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

stack resolved HBASE-1595.
--------------------------

    Resolution: Fixed
      Assignee: stack

> hadoop-default.xml and zoo.cfg in hbase jar
> -------------------------------------------
>
>                 Key: HBASE-1595
>                 URL: https://issues.apache.org/jira/browse/HBASE-1595
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.20.0
>
>
> A while back I'd added zoo.cfg to the hbase jar.  I added it at top-level.  Turns out that was wrong location.   It couldn't be found unless it was in a conf subdir.  Fellas trying to build unit tests that depended on hbase were getting this:
> {code}
> 21:31 < cwensel> adding zoo.cfg to cp gets me this: junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
> {code}
> So, I moved zoo.cfg down into conf but also moved hbase-default.xml there.  The latter was a mistake.  It should stay at top level.  In its new location, fellas were getting NPEs out of ZK Quorum Main.

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