hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gaojinchao (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4739) Master dying while going to close a region can leave it in transition forever
Date Tue, 15 Nov 2011 08:49:51 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150310#comment-13150310

gaojinchao commented on HBASE-4739:

about test failed:

  Look this comments
  public void testBlockHeapSize() {
    // We have seen multiple possible values for this estimate of the heap size
    // of a ByteBuffer, presumably depending on the JDK version.
    assertTrue(HFileBlock.BYTE_BUFFER_HEAP_SIZE == 64 ||
               HFileBlock.BYTE_BUFFER_HEAP_SIZE == 80); But in https://issues.apache.org/jira/browse/HBASE-4768

We add some code snippets´╝Ü
      assertEquals(80, HFileBlock.BYTE_BUFFER_HEAP_SIZE);
      long byteBufferExpectedSize =
          ClassSize.align(ClassSize.estimateBase(buf.getClass(), true)
              + HFileBlock.HEADER_SIZE + size);

Because we choose a rs with 0 regions.

// it said that regions is 0.
2011-11-15 03:53:11,215 INFO  [Thread-2335] master.TestDistributedLogSplitting(211): #regions
= 0
2011-11-15 03:53:11,215 DEBUG [RegionServer:0;asf001.sp2.ygridcore.net,36721,1321329179789.logSyncer]
wal.HLog$LogSyncer(1192): RegionServer:0;asf001.sp2.ygridcore.net,36721,1321329179789.logSyncer
interrupted while waiting for sync requests
2011-11-15 03:53:11,215 INFO  [RegionServer:0;asf001.sp2.ygridcore.net,36721,1321329179789.logSyncer]
wal.HLog$LogSyncer(1194): RegionServer:0;asf001.sp2.ygridcore.net,36721,1321329179789.logSyncer
2011-11-15 03:53:11,215 DEBUG [Thread-2335] wal.HLog(967): closing hlog writer in hdfs://localhost:46229/user/jenkins/.logs/asf001.sp2.ygridcore.net,36721,1321329179789
2011-11-15 03:53:11,637 DEBUG [Thread-2335] master.SplitLogManager(233): Scheduling batch
of logs to split

> Master dying while going to close a region can leave it in transition forever
> -----------------------------------------------------------------------------
>                 Key: HBASE-4739
>                 URL: https://issues.apache.org/jira/browse/HBASE-4739
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Assignee: gaojinchao
>            Priority: Minor
>             Fix For: 0.92.0, 0.94.0, 0.90.5
>         Attachments: HBASE-4739_Trunk.patch, HBASE-4739_Trunk_V2.patch
> I saw this in the aftermath of HBASE-4729 on a 0.92 refreshed yesterday, when the master
died it had just created the RIT znode for a region but didn't tell the RS to close it yet.
> When the master restarted it saw the znode and started printing this:
> {quote}
> 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentManager: Regions
in transition timed out:  TestTable,0007560564,1320253568406.f76899564cabe7e9857c3aeb526ec9dc.
state=CLOSING, ts=1320253605285, server=sv4r11s38,62003,1320195046948
> 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentManager: Region
has been CLOSING for too long, this should eventually complete or the server will expire,
doing nothing
> {quote}
> It's never going to happen, and it's blocking balancing.
> I'm marking this as minor since I believe this situation is pretty rare unless you hit
other bugs while trying out stuff to root bugs out.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message