You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Anders Brownworth <an...@gmail.com> on 2008/11/26 23:15:39 UTC

ERROR org.apache.hadoop.hbase.master.HMaster: Can not start master java.lang.reflect.InvocationTargetException - Caused by: java.net.SocketTimeoutException: timed out waiting for rpc response

Hi,

Looks like my hbase master isn't starting. Apparently an rpc is timing out
and the master never starts listening on port 60000. Looks like all the
region servers are up and running though they (obviously) can't reach the
master. Here's what I'm seeing: ("db" is 10.1.50.98)

(db:~/hbase-0.2.1) # bin/start-hbase.sh
starting master, logging to /root/hbase-0.2.1/logs/hbase-root-master-db.out
10.1.50.84: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster005.out
10.1.50.83: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster004.out
10.1.50.86: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster007.out
10.1.50.80: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster001.out
10.1.50.85: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster006.out
10.1.50.81: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster002.out
10.1.50.87: starting regionserver, logging to
/root/hbase-0.2.1/logs/hbase-root-regionserver-cluster003.out
(db:~/hbase-0.2.1) # tail -f logs/hbase-root-master-db.log
    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
    ... 6 more
Wed Nov 26 22:01:09 UTC 2008 Starting master on db
java version "1.6.0_02"
Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)
ulimit -n 1024

< some time passes here >

2008-11-26 22:02:11,018 ERROR org.apache.hadoop.hbase.master.HMaster: Can
not start master
java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:798)
    at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:832)
Caused by: java.net.SocketTimeoutException: timed out waiting for rpc
response
    at org.apache.hadoop.ipc.Client.call(Client.java:559)
    at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:212)
    at org.apache.hadoop.dfs.$Proxy0.getProtocolVersion(Unknown Source)
    at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:313)
    at org.apache.hadoop.dfs.DFSClient.createRPCNamenode(DFSClient.java:102)
    at org.apache.hadoop.dfs.DFSClient.<init>(DFSClient.java:178)
    at
org.apache.hadoop.dfs.DistributedFileSystem.initialize(DistributedFileSystem.java:68)
    at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1280)
    at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:56)
    at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1291)
    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
    ... 6 more

(db:~/hbase-0.2.1) # cat conf/hbase-site.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration>
  <property>
    <name>hbase.master</name>
    <value>10.1.50.98:60000</value>
    <description>The host and port that the HBase master runs
at.</description>
  </property>
  <property>
    <name>hbase.rootdir</name>
    <value>hdfs://10.1.50.98:50000/hbase</value>
    <description>The directory shared by region servers.</description>
  </property>
</configuration>
(db:~/hbase-0.2.1) # cat conf/regionservers
10.1.50.80
10.1.50.81
10.1.50.87
10.1.50.83
10.1.50.84
10.1.50.85
10.1.50.86
(db:~/hbase-0.2.1) #

DFS is up and running and I am able to read and write files. (both hadoop
and hbase are running on each "slave" machine) Does anyone know what RPC
call it is thats timing out here?

Thanks for your time.

-- 
-Anders
-----------------------------------------------------------
Anders Brownworth
http://www.anders.com/
anders94@gmail.com

Re: ERROR org.apache.hadoop.hbase.master.HMaster: Can not start master java.lang.reflect.InvocationTargetException - Caused by: java.net.SocketTimeoutException: timed out waiting for rpc response

Posted by stack <st...@duboce.net>.
Sorry about that.  Our versions are a little messy.   See here for an
attempt at explaination: http://wiki.apache.org/hadoop/Hbase/FAQ#19.

St.Ack

On Wed, Nov 26, 2008 at 3:47 PM, Anders Brownworth <an...@gmail.com>wrote:

> Thanks, that's it. My mistake. Something starting with "hbase-0.2"
> deceptively looked newer to me at a glance than something starting with
> "hbase-0.1".
>
> Thanks for the help.
>
> -Anders
>
> On Wed, Nov 26, 2008 at 6:20 PM, stack <st...@duboce.net> wrote:
>
> > A few preliminaries:
> >
> > + 0.2.1 hbase runs on hadoop 0.17
> > + Can you run a later hbase?
> > + Would suggest you not run as 'root'.
> >
> > A failure of rpc to work at all is usually a mistmatch in versions
> whether
> > of hadoop and hbase or perhaps master and regionservers are of different
> > versions.  Make sure you don't have any older hbase/hadoop in your
> > CLASSPATH
> > or in any of your lib dirs.
> >
> > St.Ack
> >
> >
> > On Wed, Nov 26, 2008 at 2:15 PM, Anders Brownworth <anders94@gmail.com
> > >wrote:
> >
> > > Hi,
> > >
> > > Looks like my hbase master isn't starting. Apparently an rpc is timing
> > out
> > > and the master never starts listening on port 60000. Looks like all the
> > > region servers are up and running though they (obviously) can't reach
> the
> > > master. Here's what I'm seeing: ("db" is 10.1.50.98)
> > >
> > > (db:~/hbase-0.2.1) # bin/start-hbase.sh
> > > starting master, logging to
> > /root/hbase-0.2.1/logs/hbase-root-master-db.out
> > > 10.1.50.84: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster005.out
> > > 10.1.50.83: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster004.out
> > > 10.1.50.86: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster007.out
> > > 10.1.50.80: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster001.out
> > > 10.1.50.85: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster006.out
> > > 10.1.50.81: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster002.out
> > > 10.1.50.87: starting regionserver, logging to
> > > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster003.out
> > > (db:~/hbase-0.2.1) # tail -f logs/hbase-root-master-db.log
> > >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
> > >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
> > >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
> > >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
> > >    ... 6 more
> > > Wed Nov 26 22:01:09 UTC 2008 Starting master on db
> > > java version "1.6.0_02"
> > > Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> > > Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)
> > > ulimit -n 1024
> > >
> > > < some time passes here >
> > >
> > > 2008-11-26 22:02:11,018 ERROR org.apache.hadoop.hbase.master.HMaster:
> Can
> > > not start master
> > > java.lang.reflect.InvocationTargetException
> > >    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> > Method)
> > >    at
> > >
> > >
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> > >    at
> > >
> > >
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> > >    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> > >    at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:798)
> > >    at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:832)
> > > Caused by: java.net.SocketTimeoutException: timed out waiting for rpc
> > > response
> > >    at org.apache.hadoop.ipc.Client.call(Client.java:559)
> > >    at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:212)
> > >    at org.apache.hadoop.dfs.$Proxy0.getProtocolVersion(Unknown Source)
> > >    at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:313)
> > >    at
> > org.apache.hadoop.dfs.DFSClient.createRPCNamenode(DFSClient.java:102)
> > >    at org.apache.hadoop.dfs.DFSClient.<init>(DFSClient.java:178)
> > >    at
> > >
> > >
> >
> org.apache.hadoop.dfs.DistributedFileSystem.initialize(DistributedFileSystem.java:68)
> > >    at
> > > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1280)
> > >    at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:56)
> > >    at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1291)
> > >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
> > >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
> > >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
> > >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
> > >    ... 6 more
> > >
> > > (db:~/hbase-0.2.1) # cat conf/hbase-site.xml
> > > <?xml version="1.0"?>
> > > <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> > > <configuration>
> > >  <property>
> > >    <name>hbase.master</name>
> > >    <value>10.1.50.98:60000</value>
> > >    <description>The host and port that the HBase master runs
> > > at.</description>
> > >  </property>
> > >  <property>
> > >    <name>hbase.rootdir</name>
> > >    <value>hdfs://10.1.50.98:50000/hbase</value>
> > >    <description>The directory shared by region servers.</description>
> > >  </property>
> > > </configuration>
> > > (db:~/hbase-0.2.1) # cat conf/regionservers
> > > 10.1.50.80
> > > 10.1.50.81
> > > 10.1.50.87
> > > 10.1.50.83
> > > 10.1.50.84
> > > 10.1.50.85
> > > 10.1.50.86
> > > (db:~/hbase-0.2.1) #
> > >
> > > DFS is up and running and I am able to read and write files. (both
> hadoop
> > > and hbase are running on each "slave" machine) Does anyone know what
> RPC
> > > call it is thats timing out here?
> > >
> > > Thanks for your time.
> > >
> > > --
> > > -Anders
> > > -----------------------------------------------------------
> > > Anders Brownworth
> > > http://www.anders.com/
> > > anders94@gmail.com
> > >
> >
>
>
>
> --
> -Anders
> -----------------------------------------------------------
> Anders Brownworth
> http://www.anders.com/
> anders94@gmail.com
>

Re: ERROR org.apache.hadoop.hbase.master.HMaster: Can not start master java.lang.reflect.InvocationTargetException - Caused by: java.net.SocketTimeoutException: timed out waiting for rpc response

Posted by Anders Brownworth <an...@gmail.com>.
Thanks, that's it. My mistake. Something starting with "hbase-0.2"
deceptively looked newer to me at a glance than something starting with
"hbase-0.1".

Thanks for the help.

-Anders

On Wed, Nov 26, 2008 at 6:20 PM, stack <st...@duboce.net> wrote:

> A few preliminaries:
>
> + 0.2.1 hbase runs on hadoop 0.17
> + Can you run a later hbase?
> + Would suggest you not run as 'root'.
>
> A failure of rpc to work at all is usually a mistmatch in versions whether
> of hadoop and hbase or perhaps master and regionservers are of different
> versions.  Make sure you don't have any older hbase/hadoop in your
> CLASSPATH
> or in any of your lib dirs.
>
> St.Ack
>
>
> On Wed, Nov 26, 2008 at 2:15 PM, Anders Brownworth <anders94@gmail.com
> >wrote:
>
> > Hi,
> >
> > Looks like my hbase master isn't starting. Apparently an rpc is timing
> out
> > and the master never starts listening on port 60000. Looks like all the
> > region servers are up and running though they (obviously) can't reach the
> > master. Here's what I'm seeing: ("db" is 10.1.50.98)
> >
> > (db:~/hbase-0.2.1) # bin/start-hbase.sh
> > starting master, logging to
> /root/hbase-0.2.1/logs/hbase-root-master-db.out
> > 10.1.50.84: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster005.out
> > 10.1.50.83: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster004.out
> > 10.1.50.86: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster007.out
> > 10.1.50.80: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster001.out
> > 10.1.50.85: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster006.out
> > 10.1.50.81: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster002.out
> > 10.1.50.87: starting regionserver, logging to
> > /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster003.out
> > (db:~/hbase-0.2.1) # tail -f logs/hbase-root-master-db.log
> >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
> >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
> >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
> >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
> >    ... 6 more
> > Wed Nov 26 22:01:09 UTC 2008 Starting master on db
> > java version "1.6.0_02"
> > Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> > Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)
> > ulimit -n 1024
> >
> > < some time passes here >
> >
> > 2008-11-26 22:02:11,018 ERROR org.apache.hadoop.hbase.master.HMaster: Can
> > not start master
> > java.lang.reflect.InvocationTargetException
> >    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> >    at
> >
> >
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> >    at
> >
> >
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> >    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> >    at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:798)
> >    at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:832)
> > Caused by: java.net.SocketTimeoutException: timed out waiting for rpc
> > response
> >    at org.apache.hadoop.ipc.Client.call(Client.java:559)
> >    at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:212)
> >    at org.apache.hadoop.dfs.$Proxy0.getProtocolVersion(Unknown Source)
> >    at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:313)
> >    at
> org.apache.hadoop.dfs.DFSClient.createRPCNamenode(DFSClient.java:102)
> >    at org.apache.hadoop.dfs.DFSClient.<init>(DFSClient.java:178)
> >    at
> >
> >
> org.apache.hadoop.dfs.DistributedFileSystem.initialize(DistributedFileSystem.java:68)
> >    at
> > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1280)
> >    at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:56)
> >    at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1291)
> >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
> >    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
> >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
> >    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
> >    ... 6 more
> >
> > (db:~/hbase-0.2.1) # cat conf/hbase-site.xml
> > <?xml version="1.0"?>
> > <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> > <configuration>
> >  <property>
> >    <name>hbase.master</name>
> >    <value>10.1.50.98:60000</value>
> >    <description>The host and port that the HBase master runs
> > at.</description>
> >  </property>
> >  <property>
> >    <name>hbase.rootdir</name>
> >    <value>hdfs://10.1.50.98:50000/hbase</value>
> >    <description>The directory shared by region servers.</description>
> >  </property>
> > </configuration>
> > (db:~/hbase-0.2.1) # cat conf/regionservers
> > 10.1.50.80
> > 10.1.50.81
> > 10.1.50.87
> > 10.1.50.83
> > 10.1.50.84
> > 10.1.50.85
> > 10.1.50.86
> > (db:~/hbase-0.2.1) #
> >
> > DFS is up and running and I am able to read and write files. (both hadoop
> > and hbase are running on each "slave" machine) Does anyone know what RPC
> > call it is thats timing out here?
> >
> > Thanks for your time.
> >
> > --
> > -Anders
> > -----------------------------------------------------------
> > Anders Brownworth
> > http://www.anders.com/
> > anders94@gmail.com
> >
>



-- 
-Anders
-----------------------------------------------------------
Anders Brownworth
http://www.anders.com/
anders94@gmail.com

Re: ERROR org.apache.hadoop.hbase.master.HMaster: Can not start master java.lang.reflect.InvocationTargetException - Caused by: java.net.SocketTimeoutException: timed out waiting for rpc response

Posted by stack <st...@duboce.net>.
A few preliminaries:

+ 0.2.1 hbase runs on hadoop 0.17
+ Can you run a later hbase?
+ Would suggest you not run as 'root'.

A failure of rpc to work at all is usually a mistmatch in versions whether
of hadoop and hbase or perhaps master and regionservers are of different
versions.  Make sure you don't have any older hbase/hadoop in your CLASSPATH
or in any of your lib dirs.

St.Ack


On Wed, Nov 26, 2008 at 2:15 PM, Anders Brownworth <an...@gmail.com>wrote:

> Hi,
>
> Looks like my hbase master isn't starting. Apparently an rpc is timing out
> and the master never starts listening on port 60000. Looks like all the
> region servers are up and running though they (obviously) can't reach the
> master. Here's what I'm seeing: ("db" is 10.1.50.98)
>
> (db:~/hbase-0.2.1) # bin/start-hbase.sh
> starting master, logging to /root/hbase-0.2.1/logs/hbase-root-master-db.out
> 10.1.50.84: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster005.out
> 10.1.50.83: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster004.out
> 10.1.50.86: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster007.out
> 10.1.50.80: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster001.out
> 10.1.50.85: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster006.out
> 10.1.50.81: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster002.out
> 10.1.50.87: starting regionserver, logging to
> /root/hbase-0.2.1/logs/hbase-root-regionserver-cluster003.out
> (db:~/hbase-0.2.1) # tail -f logs/hbase-root-master-db.log
>    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
>    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
>    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
>    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
>    ... 6 more
> Wed Nov 26 22:01:09 UTC 2008 Starting master on db
> java version "1.6.0_02"
> Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)
> ulimit -n 1024
>
> < some time passes here >
>
> 2008-11-26 22:02:11,018 ERROR org.apache.hadoop.hbase.master.HMaster: Can
> not start master
> java.lang.reflect.InvocationTargetException
>    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>    at
>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>    at
>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>    at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:798)
>    at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:832)
> Caused by: java.net.SocketTimeoutException: timed out waiting for rpc
> response
>    at org.apache.hadoop.ipc.Client.call(Client.java:559)
>    at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:212)
>    at org.apache.hadoop.dfs.$Proxy0.getProtocolVersion(Unknown Source)
>    at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:313)
>    at org.apache.hadoop.dfs.DFSClient.createRPCNamenode(DFSClient.java:102)
>    at org.apache.hadoop.dfs.DFSClient.<init>(DFSClient.java:178)
>    at
>
> org.apache.hadoop.dfs.DistributedFileSystem.initialize(DistributedFileSystem.java:68)
>    at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1280)
>    at org.apache.hadoop.fs.FileSystem.access$300(FileSystem.java:56)
>    at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1291)
>    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:203)
>    at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:108)
>    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:178)
>    at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:148)
>    ... 6 more
>
> (db:~/hbase-0.2.1) # cat conf/hbase-site.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <configuration>
>  <property>
>    <name>hbase.master</name>
>    <value>10.1.50.98:60000</value>
>    <description>The host and port that the HBase master runs
> at.</description>
>  </property>
>  <property>
>    <name>hbase.rootdir</name>
>    <value>hdfs://10.1.50.98:50000/hbase</value>
>    <description>The directory shared by region servers.</description>
>  </property>
> </configuration>
> (db:~/hbase-0.2.1) # cat conf/regionservers
> 10.1.50.80
> 10.1.50.81
> 10.1.50.87
> 10.1.50.83
> 10.1.50.84
> 10.1.50.85
> 10.1.50.86
> (db:~/hbase-0.2.1) #
>
> DFS is up and running and I am able to read and write files. (both hadoop
> and hbase are running on each "slave" machine) Does anyone know what RPC
> call it is thats timing out here?
>
> Thanks for your time.
>
> --
> -Anders
> -----------------------------------------------------------
> Anders Brownworth
> http://www.anders.com/
> anders94@gmail.com
>