You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by zhang gaozhi <ga...@gmail.com> on 2008/08/18 06:04:46 UTC

Fwd:

Dear all,

       Firstly, thanks for your efforts about hbase/hadoop project, they are
the good projects and give our better understanding and help.
       When we use the hbase, create the htable and do stress testing; find
out some problems. That is , we insert the record into the htable
continually, after a period,  we meet some errors as the following
informations.


count:40186954    ( The record number inserted)

count:40186955    ( The record number inserted)

count:40186956    ( The record number inserted)

count:40186957    ( The record number inserted)

Exception in thread "main"
org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact
region server 192.168.209.37:60020 for region
imlogs1,37415117,1218859785143, row '40186957', but failed after 10
attempts.

Exceptions:

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response

java.net.SocketTimeoutException: timed out waiting for rpc response



        at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServerWithRetries(HConnectionManager.java:892)

        at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1168)

        at org.apache.hadoop.hbase.PutImData1.main(PutImData1.java:192)


        As above shown,  if any problems,  how to do for fixing the
problems. By the way, can send our  some your stress testing results and
give our better suggestions.

      The table used in our testbed shown:

       hbase(main):015:0> describe 'imlogs'

{NAME => 'imlogs', IS_ROOT => 'false', IS_META => 'false', FAMILIES =>
[{NAME => 'reciever', BLOOMFILTER => 'f

alse', VERSIONS => '999999999', COMPRESSION => 'NONE', LENGTH =>
'2147483647', TTL => '-1', IN_MEMORY => 'fals

e', BLOCKCACHE => 'false'}, {NAME => 'sender', BLOOMFILTER => 'false',
VERSIONS => '999999999', COMPRESSION =>

 'NONE', LENGTH => '2147483647', TTL => '-1', IN_MEMORY => 'false',
BLOCKCACHE => 'false'}, {NAME => 'content'

, BLOOMFILTER => 'false', VERSIONS => '999999999', COMPRESSION => 'NONE',
LENGTH => '2147483647', TTL => '-1',

 IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}


                                                       Best regards

thanks

gaozhi

Re:

Posted by Jean-Daniel Cryans <jd...@gmail.com>.
gaozhi,

The NotServingRegionException is normal. After a region's split, the client
cache will have the old information and will update it upon getting this
exception. Can we see a bigger part of your logs? Maybe around when you get
all your RPC timeouts?

Thx,

J-D

On Mon, Aug 18, 2008 at 10:10 PM, zhongbai.zhou <zh...@teltel.com>wrote:

> Hi,
> 1. Test environment
> * OS : Centos 3.8
> * Machines: i386(CPU:P43.0,MEM:1G,HD:40G)
> * Hadoop version : 0.17.1
> * HBase version : 0.2.0
> - HBase: 1 HMaster and 4 regionservers
> - Hadoop: 1 master and 4 slaves of HDFS (at first, I started test with 1
> master and 1 slave of HDFS)
>
> Machines Ip:
> --- 192.168.209.37
> --- 192.168.209.33
> --- 192.168.209.41
> --- 192.168.209.42
>
>
> Flow : 192.168.209.37 log
> 2008-08-15 21:57:45,057 INFO org.apache.hadoop.ipc.Server: IPC Server
> handler 4 on 60020, call batchUpdate([B@cdfebd, row => 25662854, {column
> =>
> session:25662854, value => '...'}) from 192.168.209.37:59006: error:
> org.apache.hadoop.hbase.NotServingRegionException:
> usersessions1,23002845,1218802970003
>
> org.apache.hadoop.hbase.NotServingRegionException:
> usersessions1,23002845,1218802970003
>
>        at
>
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.j
> ava:1436)
>
>        at
>
> org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer
> .java:1147)
>
>        at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
>
>        at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
>
>        at java.lang.reflect.Method.invoke(Method.java:597)
>
>        at
> org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:473)
>
>        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:896)
>
> 2008-08-15 21:57:45,067 INFO org.apache.hadoop.ipc.Server: IPC Server
> handler 8 on 60020, call batchUpdate([B@5d66be, row => 25201453, {column
> =>
> session:25201453, value => '...'}) from 192.168.209.37:59007: error:
> org.apache.hadoop.hbase.NotServingRegionException:
> usersessions1,23002845,1218802970003
>
> org.apache.hadoop.hbase.NotServingRegionException:
> usersessions1,23002845,1218802970003
>
>        at
>
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.j
> ava:1436)
>
>        at
>
> org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer
> .java:1147)
>
>        at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
>
>        at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
>
>        at java.lang.reflect.Method.invoke(Method.java:597)
>
>        at
> org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:473)
>
>        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:896)
>
>
> -----邮件原件-----
> 发件人: Jean-Daniel Cryans [mailto:jdcryans@gmail.com]
> 发送时间: 2008年8月19日 4:32
> 收件人: hbase-user@hadoop.apache.org; hbase-dev@hadoop.apache.org
> 主题: Re:
>
> gaozhi,
>
> What is your setup like? How many regionservers? Is it in a VM? What are
> your machines like? Have you checked in your node's (192.168.209.37) logs
> to
> see if there is anything anormal? Can you send an excerpt? Which version of
> Hadoop/HBase?
>
> Getting your insertion code would also be nice.
>
> Thx
>
> J-D
>
> P.S. I sent this to the user mailing list since this is not
> development-related.
>
> On Mon, Aug 18, 2008 at 12:04 AM, zhang gaozhi
> <ga...@gmail.com>wrote:
>
> > Dear all,
> >
> >        Firstly, thanks for your efforts about hbase/hadoop project, they
> > are the good projects and give our better understanding and help.
> >        When we use the hbase, create the htable and do stress testing;
> find
> > out some problems. That is , we insert the record into the htable
> > continually, after a period,  we meet some errors as the following
> > informations.
> >
> >
> > count:40186954    ( The record number inserted)
> >
> > count:40186955    ( The record number inserted)
> >
> > count:40186956    ( The record number inserted)
> >
> > count:40186957    ( The record number inserted)
> >
> > Exception in thread "main"
> > org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to
> contact
> > region server 192.168.209.37:60020 for region
> > imlogs1,37415117,1218859785143, row '40186957', but failed after 10
> > attempts.
> >
> > Exceptions:
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> > java.net.SocketTimeoutException: timed out waiting for rpc response
> >
> >
> >
> >         at
> >
>
> org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServ
> erWithRetries(HConnectionManager.java:892)
> >
> >         at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1168)
> >
> >         at org.apache.hadoop.hbase.PutImData1.main(PutImData1.java:192)
> >
> >
> >         As above shown,  if any problems,  how to do for fixing the
> > problems. By the way, can send our  some your stress testing results and
> > give our better suggestions.
> >
> >       The table used in our testbed shown:
> >
> >        hbase(main):015:0> describe 'imlogs'
> >
> > {NAME => 'imlogs', IS_ROOT => 'false', IS_META => 'false', FAMILIES =>
> > [{NAME => 'reciever', BLOOMFILTER => 'f
> >
> > alse', VERSIONS => '999999999', COMPRESSION => 'NONE', LENGTH =>
> > '2147483647', TTL => '-1', IN_MEMORY => 'fals
> >
> > e', BLOCKCACHE => 'false'}, {NAME => 'sender', BLOOMFILTER => 'false',
> > VERSIONS => '999999999', COMPRESSION =>
> >
> >  'NONE', LENGTH => '2147483647', TTL => '-1', IN_MEMORY => 'false',
> > BLOCKCACHE => 'false'}, {NAME => 'content'
> >
> > , BLOOMFILTER => 'false', VERSIONS => '999999999', COMPRESSION => 'NONE',
> > LENGTH => '2147483647', TTL => '-1',
> >
> >  IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}
> >
> >
> >                                                         Best regards
> >
> > thanks
> >
> > gaozhi
> >
> >
> >
> >
> >
> >
>
>

Re:

Posted by "zhongbai.zhou" <zh...@teltel.com>.
Hi,
1. Test environment
* OS : Centos 3.8
* Machines: i386(CPU:P43.0,MEM:1G,HD:40G)
* Hadoop version : 0.17.1
* HBase version : 0.2.0
- HBase: 1 HMaster and 4 regionservers
- Hadoop: 1 master and 4 slaves of HDFS (at first, I started test with 1
master and 1 slave of HDFS)

Machines Ip:
--- 192.168.209.37
--- 192.168.209.33
--- 192.168.209.41
--- 192.168.209.42


Flow : 192.168.209.37 log
2008-08-15 21:57:45,057 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 4 on 60020, call batchUpdate([B@cdfebd, row => 25662854, {column =>
session:25662854, value => '...'}) from 192.168.209.37:59006: error:
org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.j
ava:1436)

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer
.java:1147)

        at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at
org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:473)

        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:896)

2008-08-15 21:57:45,067 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 8 on 60020, call batchUpdate([B@5d66be, row => 25201453, {column =>
session:25201453, value => '...'}) from 192.168.209.37:59007: error:
org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.j
ava:1436)

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer
.java:1147)

        at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at
org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:473)

        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:896)


-----邮件原件-----
发件人: Jean-Daniel Cryans [mailto:jdcryans@gmail.com] 
发送时间: 2008年8月19日 4:32
收件人: hbase-user@hadoop.apache.org; hbase-dev@hadoop.apache.org
主题: Re:

gaozhi,

What is your setup like? How many regionservers? Is it in a VM? What are
your machines like? Have you checked in your node's (192.168.209.37) logs to
see if there is anything anormal? Can you send an excerpt? Which version of
Hadoop/HBase?

Getting your insertion code would also be nice.

Thx

J-D

P.S. I sent this to the user mailing list since this is not
development-related.

On Mon, Aug 18, 2008 at 12:04 AM, zhang gaozhi
<ga...@gmail.com>wrote:

> Dear all,
>
>        Firstly, thanks for your efforts about hbase/hadoop project, they
> are the good projects and give our better understanding and help.
>        When we use the hbase, create the htable and do stress testing;
find
> out some problems. That is , we insert the record into the htable
> continually, after a period,  we meet some errors as the following
> informations.
>
>
> count:40186954    ( The record number inserted)
>
> count:40186955    ( The record number inserted)
>
> count:40186956    ( The record number inserted)
>
> count:40186957    ( The record number inserted)
>
> Exception in thread "main"
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to
contact
> region server 192.168.209.37:60020 for region
> imlogs1,37415117,1218859785143, row '40186957', but failed after 10
> attempts.
>
> Exceptions:
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
>
>
>         at
>
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServ
erWithRetries(HConnectionManager.java:892)
>
>         at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1168)
>
>         at org.apache.hadoop.hbase.PutImData1.main(PutImData1.java:192)
>
>
>         As above shown,  if any problems,  how to do for fixing the
> problems. By the way, can send our  some your stress testing results and
> give our better suggestions.
>
>       The table used in our testbed shown:
>
>        hbase(main):015:0> describe 'imlogs'
>
> {NAME => 'imlogs', IS_ROOT => 'false', IS_META => 'false', FAMILIES =>
> [{NAME => 'reciever', BLOOMFILTER => 'f
>
> alse', VERSIONS => '999999999', COMPRESSION => 'NONE', LENGTH =>
> '2147483647', TTL => '-1', IN_MEMORY => 'fals
>
> e', BLOCKCACHE => 'false'}, {NAME => 'sender', BLOOMFILTER => 'false',
> VERSIONS => '999999999', COMPRESSION =>
>
>  'NONE', LENGTH => '2147483647', TTL => '-1', IN_MEMORY => 'false',
> BLOCKCACHE => 'false'}, {NAME => 'content'
>
> , BLOOMFILTER => 'false', VERSIONS => '999999999', COMPRESSION => 'NONE',
> LENGTH => '2147483647', TTL => '-1',
>
>  IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}
>
>
>                                                         Best regards
>
> thanks
>
> gaozhi
>
>
>
>
>
>


Re:

Posted by "zhongbai.zhou" <zh...@teltel.com>.
Hi,
1. Test environment
* OS : Centos 3.8
* Machines: i386(CPU:P43.0,MEM:1G,HD:40G)
* Hadoop version : 0.17.1
* HBase version : 0.2.0
- HBase: 1 HMaster and 4 regionservers
- Hadoop: 1 master and 4 slaves of HDFS (at first, I started test with 1
master and 1 slave of HDFS)

Machines Ip:
--- 192.168.209.37
--- 192.168.209.33
--- 192.168.209.41
--- 192.168.209.42


Flow : 192.168.209.37 log
2008-08-15 21:57:45,057 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 4 on 60020, call batchUpdate([B@cdfebd, row => 25662854, {column =>
session:25662854, value => '...'}) from 192.168.209.37:59006: error:
org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.j
ava:1436)

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer
.java:1147)

        at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at
org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:473)

        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:896)

2008-08-15 21:57:45,067 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 8 on 60020, call batchUpdate([B@5d66be, row => 25201453, {column =>
session:25201453, value => '...'}) from 192.168.209.37:59007: error:
org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

org.apache.hadoop.hbase.NotServingRegionException:
usersessions1,23002845,1218802970003

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.j
ava:1436)

        at
org.apache.hadoop.hbase.regionserver.HRegionServer.batchUpdate(HRegionServer
.java:1147)

        at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at
org.apache.hadoop.hbase.ipc.HbaseRPC$Server.call(HbaseRPC.java:473)

        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:896)


-----邮件原件-----
发件人: Jean-Daniel Cryans [mailto:jdcryans@gmail.com] 
发送时间: 2008年8月19日 4:32
收件人: hbase-user@hadoop.apache.org; hbase-dev@hadoop.apache.org
主题: Re:

gaozhi,

What is your setup like? How many regionservers? Is it in a VM? What are
your machines like? Have you checked in your node's (192.168.209.37) logs to
see if there is anything anormal? Can you send an excerpt? Which version of
Hadoop/HBase?

Getting your insertion code would also be nice.

Thx

J-D

P.S. I sent this to the user mailing list since this is not
development-related.

On Mon, Aug 18, 2008 at 12:04 AM, zhang gaozhi
<ga...@gmail.com>wrote:

> Dear all,
>
>        Firstly, thanks for your efforts about hbase/hadoop project, they
> are the good projects and give our better understanding and help.
>        When we use the hbase, create the htable and do stress testing;
find
> out some problems. That is , we insert the record into the htable
> continually, after a period,  we meet some errors as the following
> informations.
>
>
> count:40186954    ( The record number inserted)
>
> count:40186955    ( The record number inserted)
>
> count:40186956    ( The record number inserted)
>
> count:40186957    ( The record number inserted)
>
> Exception in thread "main"
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to
contact
> region server 192.168.209.37:60020 for region
> imlogs1,37415117,1218859785143, row '40186957', but failed after 10
> attempts.
>
> Exceptions:
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
>
>
>         at
>
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServ
erWithRetries(HConnectionManager.java:892)
>
>         at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1168)
>
>         at org.apache.hadoop.hbase.PutImData1.main(PutImData1.java:192)
>
>
>         As above shown,  if any problems,  how to do for fixing the
> problems. By the way, can send our  some your stress testing results and
> give our better suggestions.
>
>       The table used in our testbed shown:
>
>        hbase(main):015:0> describe 'imlogs'
>
> {NAME => 'imlogs', IS_ROOT => 'false', IS_META => 'false', FAMILIES =>
> [{NAME => 'reciever', BLOOMFILTER => 'f
>
> alse', VERSIONS => '999999999', COMPRESSION => 'NONE', LENGTH =>
> '2147483647', TTL => '-1', IN_MEMORY => 'fals
>
> e', BLOCKCACHE => 'false'}, {NAME => 'sender', BLOOMFILTER => 'false',
> VERSIONS => '999999999', COMPRESSION =>
>
>  'NONE', LENGTH => '2147483647', TTL => '-1', IN_MEMORY => 'false',
> BLOCKCACHE => 'false'}, {NAME => 'content'
>
> , BLOOMFILTER => 'false', VERSIONS => '999999999', COMPRESSION => 'NONE',
> LENGTH => '2147483647', TTL => '-1',
>
>  IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}
>
>
>                                                         Best regards
>
> thanks
>
> gaozhi
>
>
>
>
>
>


Re:

Posted by Jean-Daniel Cryans <jd...@gmail.com>.
gaozhi,

What is your setup like? How many regionservers? Is it in a VM? What are
your machines like? Have you checked in your node's (192.168.209.37) logs to
see if there is anything anormal? Can you send an excerpt? Which version of
Hadoop/HBase?

Getting your insertion code would also be nice.

Thx

J-D

P.S. I sent this to the user mailing list since this is not
development-related.

On Mon, Aug 18, 2008 at 12:04 AM, zhang gaozhi <ga...@gmail.com>wrote:

> Dear all,
>
>        Firstly, thanks for your efforts about hbase/hadoop project, they
> are the good projects and give our better understanding and help.
>        When we use the hbase, create the htable and do stress testing; find
> out some problems. That is , we insert the record into the htable
> continually, after a period,  we meet some errors as the following
> informations.
>
>
> count:40186954    ( The record number inserted)
>
> count:40186955    ( The record number inserted)
>
> count:40186956    ( The record number inserted)
>
> count:40186957    ( The record number inserted)
>
> Exception in thread "main"
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact
> region server 192.168.209.37:60020 for region
> imlogs1,37415117,1218859785143, row '40186957', but failed after 10
> attempts.
>
> Exceptions:
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
>
>
>         at
> org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServerWithRetries(HConnectionManager.java:892)
>
>         at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1168)
>
>         at org.apache.hadoop.hbase.PutImData1.main(PutImData1.java:192)
>
>
>         As above shown,  if any problems,  how to do for fixing the
> problems. By the way, can send our  some your stress testing results and
> give our better suggestions.
>
>       The table used in our testbed shown:
>
>        hbase(main):015:0> describe 'imlogs'
>
> {NAME => 'imlogs', IS_ROOT => 'false', IS_META => 'false', FAMILIES =>
> [{NAME => 'reciever', BLOOMFILTER => 'f
>
> alse', VERSIONS => '999999999', COMPRESSION => 'NONE', LENGTH =>
> '2147483647', TTL => '-1', IN_MEMORY => 'fals
>
> e', BLOCKCACHE => 'false'}, {NAME => 'sender', BLOOMFILTER => 'false',
> VERSIONS => '999999999', COMPRESSION =>
>
>  'NONE', LENGTH => '2147483647', TTL => '-1', IN_MEMORY => 'false',
> BLOCKCACHE => 'false'}, {NAME => 'content'
>
> , BLOOMFILTER => 'false', VERSIONS => '999999999', COMPRESSION => 'NONE',
> LENGTH => '2147483647', TTL => '-1',
>
>  IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}
>
>
>                                                         Best regards
>
> thanks
>
> gaozhi
>
>
>
>
>
>

Re:

Posted by Jean-Daniel Cryans <jd...@gmail.com>.
gaozhi,

What is your setup like? How many regionservers? Is it in a VM? What are
your machines like? Have you checked in your node's (192.168.209.37) logs to
see if there is anything anormal? Can you send an excerpt? Which version of
Hadoop/HBase?

Getting your insertion code would also be nice.

Thx

J-D

P.S. I sent this to the user mailing list since this is not
development-related.

On Mon, Aug 18, 2008 at 12:04 AM, zhang gaozhi <ga...@gmail.com>wrote:

> Dear all,
>
>        Firstly, thanks for your efforts about hbase/hadoop project, they
> are the good projects and give our better understanding and help.
>        When we use the hbase, create the htable and do stress testing; find
> out some problems. That is , we insert the record into the htable
> continually, after a period,  we meet some errors as the following
> informations.
>
>
> count:40186954    ( The record number inserted)
>
> count:40186955    ( The record number inserted)
>
> count:40186956    ( The record number inserted)
>
> count:40186957    ( The record number inserted)
>
> Exception in thread "main"
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact
> region server 192.168.209.37:60020 for region
> imlogs1,37415117,1218859785143, row '40186957', but failed after 10
> attempts.
>
> Exceptions:
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
> java.net.SocketTimeoutException: timed out waiting for rpc response
>
>
>
>         at
> org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getRegionServerWithRetries(HConnectionManager.java:892)
>
>         at org.apache.hadoop.hbase.client.HTable.commit(HTable.java:1168)
>
>         at org.apache.hadoop.hbase.PutImData1.main(PutImData1.java:192)
>
>
>         As above shown,  if any problems,  how to do for fixing the
> problems. By the way, can send our  some your stress testing results and
> give our better suggestions.
>
>       The table used in our testbed shown:
>
>        hbase(main):015:0> describe 'imlogs'
>
> {NAME => 'imlogs', IS_ROOT => 'false', IS_META => 'false', FAMILIES =>
> [{NAME => 'reciever', BLOOMFILTER => 'f
>
> alse', VERSIONS => '999999999', COMPRESSION => 'NONE', LENGTH =>
> '2147483647', TTL => '-1', IN_MEMORY => 'fals
>
> e', BLOCKCACHE => 'false'}, {NAME => 'sender', BLOOMFILTER => 'false',
> VERSIONS => '999999999', COMPRESSION =>
>
>  'NONE', LENGTH => '2147483647', TTL => '-1', IN_MEMORY => 'false',
> BLOCKCACHE => 'false'}, {NAME => 'content'
>
> , BLOOMFILTER => 'false', VERSIONS => '999999999', COMPRESSION => 'NONE',
> LENGTH => '2147483647', TTL => '-1',
>
>  IN_MEMORY => 'false', BLOCKCACHE => 'false'}]}
>
>
>                                                         Best regards
>
> thanks
>
> gaozhi
>
>
>
>
>
>