You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2013/03/06 08:14:19 UTC
[jira] [Commented] (HBASE-6877) Coprocessor exec result is
incorrect when region is in splitting
[ https://issues.apache.org/jira/browse/HBASE-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594453#comment-13594453 ]
Andrew Purtell commented on HBASE-6877:
---------------------------------------
[~anoop.hbase] you said on dev list you are seeing this? Does applying the patch fix it for you? Presumably [~zjushch] you've fixed this locally already?
We should commit this if people are hitting it.
> 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