[
https://issues.apache.org/jira/browse/HBASE-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370975#comment-16370975
]
ramkrishna.s.vasudevan commented on HBASE-20017:
------------------------------------------------
Ok. I could see the fix branches now. Seeing the patch names I thought it is
branch-1 issue only. I spent lot of time debugging our internal branch code
thinking it was doing something wrong on server side and finally convinced
myself it is from the client or the RPC layer. But was yet to find the root
cause. Thanks for the finding.
> 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)
