You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2019/02/22 12:39:00 UTC

[jira] [Updated] (HBASE-21945) Maintain the original order when sending batch request

     [ https://issues.apache.org/jira/browse/HBASE-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang updated HBASE-21945:
------------------------------
    Summary: Maintain the original order when sending batch request  (was: Maintain the original order when send batching request)

> Maintain the original order when sending batch request
> ------------------------------------------------------
>
>                 Key: HBASE-21945
>                 URL: https://issues.apache.org/jira/browse/HBASE-21945
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>            Priority: Major
>
> Find this when implementing HBASE-21717. In some UT we put several good requests and bad requests together, and expect only the bad ones to fail. This usually depends on the grouping at rs side, if we group the good one and the bad one together as a batch, it will fail them all. So usually in test we will insert an increment or append in the middle to break them into two groups when executing at RS side.
> So if we do not maintain the order, at the rs side, the increment or append may comes first or last, then the good ones and bad ones will be grouped and cause all of them to fail.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)