[
https://issues.apache.org/jira/browse/HBASE-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371055#comment-16371055
]
Hudson commented on HBASE-20017:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #4621 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4621/])
HBASE-20017 BufferedMutatorImpl submit the same mutation repeatedly (apurtell:
rev 79d9403a79cca60e614834659e3d9005d5482cac)
* (edit)
hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestAsyncProcess.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ReaderBase.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/BufferedMutatorImpl.java
> 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)
