[
https://issues.apache.org/jira/browse/HBASE-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370962#comment-16370962
]
ramkrishna.s.vasudevan commented on HBASE-20017:
------------------------------------------------
[~chia7712]
I have not checked the code in detail but are you sure this is not there in any
of the newer branches after 1.4? In one of our internal branch based on some
old master (trunk) I found this happening. I did not dig in deep as was doing
some other things. But wanted to get back to it.
> 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: 2.0.0, 1.5.0, 1.4.2
>
> 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)
