You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/10/20 19:10:41 UTC

[jira] [Created] (HBASE-9809) RegionTooBusyException should provide region name which was too busy

Ted Yu created HBASE-9809:
-----------------------------

             Summary: RegionTooBusyException should provide region name which was too busy
                 Key: HBASE-9809
                 URL: https://issues.apache.org/jira/browse/HBASE-9809
             Project: HBase
          Issue Type: Bug
            Reporter: Ted Yu


Under this thread: http://search-hadoop.com/m/WSfKp1yJOFJ, John showed log from LoadIncrementalHFiles where the following is a snippet:
{code}
04:18:07,110  INFO LoadIncrementalHFiles:451 - Trying to load hfile=hdfs://pc08.pool.ifis.uni-luebeck.de:8020/tmp/bulkLoadDirectory/PO_S_rowBufferHFile/Hexa/_tmp/PO_S,9.bottom first=<http://purl.org/dc/elements/1.1/title>,"emulates drylot births"^^<http://www.w3.org/2001/XMLSchema#string> last=<http://purl.org/dc/e$
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=10, exceptions:
Sun Oct 20 04:15:50 CEST 2013, org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles$3@4cfdfc98, org.apache.hadoop.hbase.RegionTooBusyException: org.apache.hadoop.hbase.RegionTooBusyException: failed to get a lock in 60000ms
        at org.apache.hadoop.hbase.regionserver.HRegion.lock(HRegion.java:5778)
        at org.apache.hadoop.hbase.regionserver.HRegion.lock(HRegion.java:5764)
        at org.apache.hadoop.hbase.regionserver.HRegion.startBulkRegionOperation(HRegion.java:5723)
        at org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:3534)
        at org.apache.hadoop.hbase.regionserver.HRegion.bulkLoadHFiles(HRegion.java:3517)
        at org.apache.hadoop.hbase.regionserver.HRegionServer.bulkLoadHFiles(HRegionServer.java:2793)
        at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
{code}
Looking at the above, it is not immediately clear which region was busy.

Region name should be included in the exception so that user can correlate with the region server where the problem occurs.



--
This message was sent by Atlassian JIRA
(v6.1#6144)