Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of wenhao.xu@gmail.com designates
 74.125.82.51 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=TnJ43aPESY3Ut7/VHPTSalmpL8q7ke5DBDhChEOoEM6AcFfY97gd0VtozuQvSHWoBs
         aNgpP/xUBuCfOZ2VmQuljhUu3SC1cGY8Vy/o2/1BYGZ56ddhjSNJYexbrP2IZJN0Tz0N
         hUpeYy+9WshzFTq7DPAiPBR3svc17h9MNIeYA=
MIME-Version: 1.0
Date: Wed, 12 Jan 2011 19:13:17 +0800
Message-ID: <AANLkTi=0T9rKhDQTcNKcuyd7ZJ64gQ31mamHbLePh9Ub@mail.gmail.com>
Subject: How to avoid hole in regions with hbase 0.20.4?
From: Stanley Xu <wenhao.xu@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=0016367b62ecbf04700499a449b0

--0016367b62ecbf04700499a449b0
Content-Type: text/plain; charset=ISO-8859-1

Dear All,

We are using the hbase 0.20.4 on a project, and met the following errors
while insert/update some data to the table today:

org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact
region server Some server, retryOnlyOne=true, index=0, islastrow=false,
tries=9, numtries=10, i=0, listsize=2, region=URLTag,
http://msn.ynet.com/view.jsp\x3Foid=76005602\x26pageno=7,1294655021916<http://msn.ynet.com/view.jsp%5Cx3Foid=76005602%5Cx26pageno=7,1294655021916>
for
region URLTag,
http://msn.ent.ynet.com/view.jsp\x3Foid=49939357\x26pageno=10,1294742159472<http://msn.ent.ynet.com/view.jsp%5Cx3Foid=49939357%5Cx26pageno=10,1294742159472>,
row 'http://msn.ent.ynet.com/view.jsp\x3Foid=75954594<http://msn.ent.ynet.com/view.jsp%5Cx3Foid=75954594>',
but failed after 10 attempts.
Exceptions:

at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers$Batch.process(HConnectionManager.java:1167)
~[hbase-0.20.4.jar:na]
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.processBatchOfRows(HConnectionManager.java:1248)
~[hbase-0.20.4.jar:na]
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:666)
~[hbase-0.20.4.jar:na]
at org.apache.hadoop.hbase.client.HTable.put(HTable.java:510)
~[hbase-0.20.4.jar:na]
at
com.mediav.contextual.targeting.batch.job.HBaseTaggingJob$HBaseTaggingThread.run(HBaseTaggingJob.java:164)
~[crawler-server.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
[na:1.6.0_22]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[na:1.6.0_22]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [na:1.6.0_22]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[na:1.6.0_22]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[na:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [na:1.6.0_22]

I have searched the mail list and find the following link:
http://search-hadoop.com/m/ile3u1vHa0z1/Trying+to+contact+region+server+Some+server+0.20.4+2278&subj=error+adding+row+to+table+in+0+20+4

Which has the same log as what I met, I am wondering to know if this kind of
"hole" between regions is a bug?  Or we just use the hbase in a wrong way?
And is there anyway I could fix it except merging the regions permanently if
it is a bug in hbase? Like upgrade to a newer version of hbase?

We could fix this by merge the regions that has the problem, but I guess we
will then meet it again.

Best wishes,
Stanley Xu

--0016367b62ecbf04700499a449b0--