[
https://issues.apache.org/jira/browse/HBASE-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352976#comment-14352976
]
Ploder commented on HBASE-6877:
-------------------------------
We ran into exactly the same issue. It doesn't affect Scans, because they run
server-side. It also does not affect Gets, because they issue multiple
requests. The faulty code inside the rpc channel of the hbase client resubmits
a *single* call to a region if the region can not be found anymore on the
region server (because it was splitted in this case). However when a region has
been splitted a single call to the region server will not suffice, hence this
problem.
> Coprocessor exec result is incorrect when region is in splitting
> -----------------------------------------------------------------
>
> Key: HBASE-6877
> URL: https://issues.apache.org/jira/browse/HBASE-6877
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
> Affects Versions: 0.94.1
> Reporter: chunhui shen
> Assignee: chunhui shen
> Priority: Critical
> Attachments: HBASE-6877.patch
>
>
> When we execute the coprocessor, we will called HTable#getStartKeysInRange
> first and get the Keys to exec coprocessor,
> if then some regions are split before execCoprocessor RPC, the Keys are
> something wrong now, and the result we get is not integrated,
> for example:
> parent region is split into daughter region A and daughter region B,
> we executed coprocessor on the parent region, but the result data is only
> daughter region A or daughter region B
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
