I've found that if you remove 'src/test/resources' from your build path, things will work out better for the server testing cases. The "testing mode" settings live in the hbase-site.xml file in that dir.
You can do this by right clicking on the package in package explorer, Build Path, remove from build path. The eclipse setup generated with 'mvn eclipse:eclipse' has a build path that has hbase setup in a "unit testing mode". This is great if you want to run unit tests inside of eclipse but not good if you want to get the actual hbase servers (master, regionserver, external utils like bulk load, hfile, etc) running and debuggable. Jon On Sun, Nov 20, 2011 at 5:40 PM, 陈加俊 <[email protected]> wrote: > I run HRegionServer whith program arguments that is start in eclipse. > > 2011-11-21 09:35:12,384 WARN [main] > regionserver.HRegionServerCommandLine(56): Not starting a distinct region > server because hbase.cluster.distributed is false > > but the following contents in $HBAE_HOME/conf/hbase-site.xml : > > <property> > <name>hbase.cluster.distributed</name> > <value>true</value> > <description>The mode the cluster will be in. Possible values are > false: standalone and pseudo-distributed setups with managed Zookeeper > true: fully-distributed with unmanaged Zookeeper Quorum (see > hbase-env.sh) > </description> > </property> > -- // Jonathan Hsieh (shay) // Software Engineer, Cloudera // [email protected]
