[
https://issues.apache.org/jira/browse/HBASE-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-5986:
---------------------------------
Attachment: HBASE-5986-0.94.patch
HBASE-5986-0.92.patch
Attaching patches for 0.92 and 0.94 branches. They are direct ports of the v3
patch, but 0.92 patch also includes HRegionServer.getOnlineRegions(byte[]
tableName) function directly copied from 0.94, since we need it. I have
discovered this when testing with 0.92, so I would like it to make into it.
One minor mishap from my part is that the v3 patch which went into trunk
includes an unrelated change in RegionServerDynamicStatistics. Related issue is
HBASE-6025. Although the change is trivial ,changing
RegionServerDynamicStatistics to extend hbase-specific MetricsMBeanBase rather
than hadoop-specific MetricsDynamicMBeanBase, we may want to note this, or
revert that part. Backport patches does not include this change.
Sorry for the trouble guys.
> Clients can see holes in the META table when regions are being split
> --------------------------------------------------------------------
>
> Key: HBASE-5986
> URL: https://issues.apache.org/jira/browse/HBASE-5986
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.1, 0.96.0, 0.94.1
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.96.0
>
> Attachments: 5986-v2.txt, HBASE-5986-0.92.patch,
> HBASE-5986-0.94.patch, HBASE-5986-test_v1.patch, HBASE-5986_v3.patch
>
>
> We found this issue when running large scale ingestion tests for HBASE-5754.
> The problem is that the .META. table updates are not atomic while splitting a
> region. In SplitTransaction, there is a time lap between the marking the
> parent offline, and adding of daughters to the META table. This can result in
> clients using MetaScanner, of HTable.getStartEndKeys (used by the
> TableInputFormat) missing regions which are made just offline, but the
> daughters are not added yet.
> This is also related to HBASE-4335.
--
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
