[
https://issues.apache.org/jira/browse/HBASE-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794959#comment-13794959
]
Asaf Mesika commented on HBASE-6877:
------------------------------------
We ran into the same issue. We had to return the last rowkey was read in the
coprocessor, and check if it matched the expected region endKey. During split,
it didn't, so issue another execCoprocessor with new adjusted startKey, endKey.
It was definitely a work-around. It makes perfect sense for the execCoprocessor
to check it covered the endKey which is defined as inclusive.
I'm putting my vote here.
> 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.1#6144)
