[
https://issues.apache.org/jira/browse/HBASE-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594491#comment-13594491
]
Anoop Sam John commented on HBASE-6877:
---------------------------------------
[~apurtell] I have not hit with this issue. I was checking with HBASE-6870 and
seen this. More over I am checking the coprocessorExe code as part of test
failures with Trunk in examples module ( BulkDelete) I will be able to give the
reasoning there after some more checking.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
