hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Venkateswara Rao Dokku <dvrao....@gmail.com>
Subject Region server not able to access H-base
Date Fri, 28 Sep 2012 05:20:58 GMT
Hi,
    I crated a cluster of two nodes. One is the namenode & the other will
act asa datanode as well as region server, from the region server I
couldn't access HMaster. I was getting the following error when I try to
scan the tables on the namenode
hbase(main):001:0> scan 't1'
ROW                                COLUMN+CELL

12/09/28 10:36:38 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:41 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:43 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:46 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:49 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:52 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:58 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:36:59 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:37:01 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:37:03 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:37:06 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:37:09 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:37:13 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.
12/09/28 10:37:18 INFO ipc.HBaseRPC: Server at oc-PowerEdge-R610/
10.2.32.48:60020 could not be reached after 1 tries, giving up.

ERROR: org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed
setting up proxy interface org.apache.hadoop.hbase.ipc.HRegionInterface to
oc-PowerEdge-R610/10.2.32.48:60020 after attempts=1

Here is some help for this command:
Scan a table; pass table name and optionally a dictionary of scanner
specifications.  Scanner specifications may include one or more of:
TIMERANGE, FILTER, LIMIT, STARTROW, STOPROW, TIMESTAMP, MAXLENGTH,
or COLUMNS.

If no columns are specified, all columns will be scanned.
To scan all members of a column family, leave the qualifier empty as in
'col_family:'.

The filter can be specified in two ways:
1. Using a filterString - more information on this is available in the
Filter Language document attached to the HBASE-4176 JIRA
2. Using the entire package name of the filter.

Some examples:

  hbase> scan '.META.'
  hbase> scan '.META.', {COLUMNS => 'info:regioninfo'}
  hbase> scan 't1', {COLUMNS => ['c1', 'c2'], LIMIT => 10, STARTROW =>
'xyz'}
  hbase> scan 't1', {COLUMNS => 'c1', TIMERANGE => [1303668804, 1303668904]}
  hbase> scan 't1', {FILTER => "(PrefixFilter ('row2') AND (QualifierFilter
(>=, 'binary:xyz'))) AND (TimestampsFilter ( 123, 456))"}
  hbase> scan 't1', {FILTER =>
org.apache.hadoop.hbase.filter.ColumnPaginationFilter.new(1, 0)}

For experts, there is an additional option -- CACHE_BLOCKS -- which
switches block caching for the scanner on (true) or off (false).  By
default it is enabled.  Examples:

  hbase> scan 't1', {COLUMNS => ['c1', 'c2'], CACHE_BLOCKS => false}

& this is what I found in the region server logs
2012-09-28 10:43:41,992 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Attempting connect to
Master server at oc-PowerEdge-R610,60000,1348808587747
2012-09-28 10:44:42,830 WARN
org.apache.hadoop.hbase.regionserver.HRegionServer: Unable to connect to
master. Retrying. Error was:
java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567)
        at
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
        at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:404)
        at
org.apache.hadoop.hbase.ipc.HBaseClient$Connection.setupConnection(HBaseClient.java:328)
        at
org.apache.hadoop.hbase.ipc.HBaseClient$Connection.setupIOstreams(HBaseClient.java:362)
        at
org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1045)
        at
org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:897)
        at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Invoker.invoke(WritableRpcEngine.java:150)
        at $Proxy7.getProtocolVersion(Unknown Source)
        at
org.apache.hadoop.hbase.ipc.WritableRpcEngine.getProxy(WritableRpcEngine.java:183)
        at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:303)
        at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:280)
        at org.apache.hadoop.hbase.ipc.HBaseRPC.getProxy(HBaseRPC.java:332)
        at
org.apache.hadoop.hbase.ipc.HBaseRPC.waitForProxy(HBaseRPC.java:236)
        at
org.apache.hadoop.hbase.regionserver.HRegionServer.getMaster(HRegionServer.java:1643)
        at
org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1680)
        at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:643)
        at java.lang.Thread.run(Thread.java:662)
2012-09-28 10:44:45,831 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Attempting connect to
Master server at oc-PowerEdge-R610,60000,1348808587747
*my conf/hbase-site.xml is as given below*
*
*
<configuration>
           <property>
                                <name>hbase.master</name>
                                <value>hbase-master:60000</value>
                                <description>The host and port that the
HBase master runs at.
                                                     A value of 'local'
runs the master and a regionserver
                                                     in a single process.
                                </description>
                </property>

                <property>
                                <name>hbase.rootdir</name>

<value>hdfs://hadoop-namenode:9000/hbase</value>
                                <description>The directory shared by region
servers.</description>
                </property>

                <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>
                <property>

<name>hbase.zookeeper.property.clientPort</name>
                                <value>2222</value>
                <description>Property from ZooKeeper's config zoo.cfg.
                                The port at which the clients will connect.
                                The port at which the clients will connect.
                                </description>
                </property>

                <property>
                <name>hbase.zookeeper.quorum</name>
                <value>hbase-master</value>
                <description>Comma separated list of servers in the
ZooKeeper Quorum.
                                For example, "host1.mydomain.com,
host2.mydomain.com".
                                By default this is set to localhost for
local and
                                pseudo-distributed modes of operation. For
a fully-distributed
                                setup, this should be set to a ful list of
ZooKeeper quorum
                                servers. If HBASE_MANAGES_ZK is set in
hbase-env.sh
                                this is the list of servers which we will
start/stop ZooKeeper on.
                 </description>
                 </property>
</configuration>

I Could not connect to my HMaster on 60000, rather I can connect to it on
60010 on the namenode machine. But the region server is trying to connect
at 60000. Please help me out from this one.
my /etc/hosts file is as given below.

127.0.0.1       venkat-System-Product-Name
10.2.32.48  oc-PowerEdge-R610 hbase-master hadoop-namenode
10.240.13.54 hbase-regionserver1  hadoop-datanode1
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

-- 
Thanks & Regards,
Venkateswara Rao Dokku,
Software Engineer,One Convergence Devices Pvt Ltd.,
Jubille Hills,Hyderabad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message