[ 
https://issues.apache.org/jira/browse/HBASE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-4789:
-------------------------

    Attachment: 4789-v2.txt

Hmmm... I've been running tests w/ this patch in place and have not seen the 
issue since.  I'm going to commit this unless objection.  I don't think this 
the 'real' fix.  This patch adds a clear of the raw encoded name after we do 
the snp-encodedname remove.  We shouldn't be having to do this if our 
accounting is correct.  This patch logs when we the misaccounting so hopefully 
we'll be able to figure whats going on down the line.  Will do that in 
different issue.
                
> On split, parent region is sticking around in oldest sequenceid to region map 
> though not online; we don't cleanup WALs.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4789
>                 URL: https://issues.apache.org/jira/browse/HBASE-4789
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: 4789-v2.txt, 4789.txt
>
>
> Here is log for a particular region:
> {code}
> 2011-11-15 05:46:31,382 INFO 
> org.apache.hadoop.hbase.regionserver.SplitTransaction: Still waiting on the 
> master to process the split for 8bbd7388262dc8cb1ce2cf4f04a7281d
> 2011-11-15 05:46:31,483 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
> regionserver:7003-0x1337b0b92cd000a-0x1337b0b92cd000a Attempting to 
> transition node 8bbd7388262dc8cb1ce2cf4f04a7281d from RS_ZK_REGION_SPLIT to 
> RS_ZK_REG
> ION_SPLIT
> 2011-11-15 05:46:31,484 INFO 
> org.apache.hadoop.hbase.regionserver.SplitRequest: Region split, META 
> updated, and report to master. 
> Parent=TestTable,0862220095,1321335865649.8bbd7388262dc8cb1ce2cf4f04a7281d., 
> new regions: TestTab
> le,0862220095,1321335989689.f00c683df3182d8ef33e315f77ca539c., 
> TestTable,0892568091,1321335989689.a56ca1eff5b4401432fcba04b4e851f8.. Split 
> took 1sec
> 2011-11-15 05:46:37,705 DEBUG org.apache.hadoop.hbase.regionserver.Store: 
> Compacting 
> hdfs://sv4r11s38:7000/hbase/TestTable/a56ca1eff5b4401432fcba04b4e851f8/info/9ce16d8fa94e4938964c04775a6fa1a7.8bbd7388262dc8cb1ce2cf4f04a7281d-
> hdfs://sv4r11s38:7000/hbase/TestTable/8bbd7388262dc8cb1ce2cf4f04a7281d/info/9ce16d8fa94e4938964c04775a6fa1a7-top,
>  keycount=717559, bloomtype=NONE, size=711.1m
> 2011-11-15 05:46:37,705 DEBUG org.apache.hadoop.hbase.regionserver.Store: 
> Compacting 
> hdfs://sv4r11s38:7000/hbase/TestTable/a56ca1eff5b4401432fcba04b4e851f8/info/9213f4d7ee9b4fda857a97603a001f9e.8bbd7388262dc8cb1ce2cf4f04a7281d-
> hdfs://sv4r11s38:7000/hbase/TestTable/8bbd7388262dc8cb1ce2cf4f04a7281d/info/9213f4d7ee9b4fda857a97603a001f9e-top,
>  keycount=416691, bloomtype=NONE, size=412.9m
> 2011-11-15 05:46:53,090 DEBUG org.apache.hadoop.hbase.regionserver.Store: 
> Compacting 
> hdfs://sv4r11s38:7000/hbase/TestTable/f00c683df3182d8ef33e315f77ca539c/info/9ce16d8fa94e4938964c04775a6fa1a7.8bbd7388262dc8cb1ce2cf4f04a7281d-
> hdfs://sv4r11s38:7000/hbase/TestTable/8bbd7388262dc8cb1ce2cf4f04a7281d/info/9ce16d8fa94e4938964c04775a6fa1a7-bottom,
>  keycount=717559, bloomtype=NONE, size=711.1m
> 2011-11-15 05:46:53,090 DEBUG org.apache.hadoop.hbase.regionserver.Store: 
> Compacting 
> hdfs://sv4r11s38:7000/hbase/TestTable/f00c683df3182d8ef33e315f77ca539c/info/9213f4d7ee9b4fda857a97603a001f9e.8bbd7388262dc8cb1ce2cf4f04a7281d-
> hdfs://sv4r11s38:7000/hbase/TestTable/8bbd7388262dc8cb1ce2cf4f04a7281d/info/9213f4d7ee9b4fda857a97603a001f9e-bottom,
>  keycount=416691, bloomtype=NONE, size=412.9m
> 2011-11-15 05:48:00,690 DEBUG org.apache.hadoop.hbase.regionserver.wal.HLog: 
> Found 3 hlogs to remove out of total 12; oldest outstanding sequenceid is 
> 5699 from region 8bbd7388262dc8cb1ce2cf4f04a7281d
> 2011-11-15 05:57:54,083 INFO org.apache.hadoop.hbase.regionserver.wal.HLog: 
> Too many hlogs: logs=33, maxlogs=32; forcing flush of 1 regions(s): 
> 8bbd7388262dc8cb1ce2cf4f04a7281d
> 2011-11-15 05:57:54,083 WARN org.apache.hadoop.hbase.regionserver.LogRoller: 
> Failed to schedule flush of 8bbd7388262dc8cb1ce2cf4f04a7281dr=null, 
> requester=null
> 2011-11-15 05:58:01,358 INFO org.apache.hadoop.hbase.regionserver.wal.HLog: 
> Too many hlogs: logs=34, maxlogs=32; forcing flush of 1 regions(s): 
> 8bbd7388262dc8cb1ce2cf4f04a7281d
> 2011-11-15 05:58:01,359 WARN org.apache.hadoop.hbase.regionserver.LogRoller: 
> Failed to schedule flush of 8bbd7388262dc8cb1ce2cf4f04a7281dr=null, 
> requester=null
> {code}

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

        

Reply via email to