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 2019/02/01 20:03:00 UTC

[jira] [Updated] (HBASE-20017) BufferedMutatorImpl submit the same mutation repeatedly

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

Andrew Purtell updated HBASE-20017:
-----------------------------------
    Fix Version/s:     (was: 1.5.0)

> BufferedMutatorImpl submit the same mutation repeatedly
> -------------------------------------------------------
>
>                 Key: HBASE-20017
>                 URL: https://issues.apache.org/jira/browse/HBASE-20017
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 1.4.0, 1.4.1, 1.4.2
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Blocker
>             Fix For: 1.4.2, 2.0.0
>
>         Attachments: HBASE-20017.branch-1.4.v0.patch.patch, HBASE-20017.branch-1.v0.patch.patch, HBASE-20017.v0.patch.patch
>
>
> BMI pass a iter of inner buffer to AsyncProcess to take the undealt mutations, AsyncProcess call iter#next to get the mutation and then call iter#remove to delete the mutation from inner buffer. Hence, There's a good chance that  the mutation is processed repeatedly in case there are a bunch of threads which are running the flush.



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