[
https://issues.apache.org/jira/browse/HBASE-9730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789936#comment-13789936
]
Enis Soztutar commented on HBASE-9730:
--------------------------------------
bq. sorry, -0 for the temporary check, what is the perf implications of that?
I think we should check the region boundaries for a region operation. We cannot
rely on the client to tell the truth. We do the check in
HRegion.processRowsWithLocks() already. However, agreed that we should do this
in a separate patch.
> Exceptions in multi operations are not handled correctly
> --------------------------------------------------------
>
> Key: HBASE-9730
> URL: https://issues.apache.org/jira/browse/HBASE-9730
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9730_v1-0.96.patch, hbase-9730_v1.patch
>
>
> The symptoms are that, both ITBLL and ITLAV fail in their verification steps
> complaining about lots of undefined rows.
> {code}
> org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Verify$Counts
> REFERENCED=199619372
> UNDEFINED=190084
> UNREFERENCED=190084
> {code}
> I think the problem is in HRegionServer.doBatchOp() where in case
> HRegion.batchMutate() throws an exception, RegionActionResult indexes are not
> set correctly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
