[
https://issues.apache.org/jira/browse/HBASE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757134#comment-13757134
]
Elliott Clark commented on HBASE-9422:
--------------------------------------
Yeah it's not even that big a deal as it is. Just something I noticed while
trying to dig into the client.
Thanks.
> AsyncProcess and HTable will submit the same mutation twice if there is an
> error locating region.
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-9422
> URL: https://issues.apache.org/jira/browse/HBASE-9422
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Elliott Clark
> Assignee: Nicolas Liochon
> Priority: Minor
>
> HTable#backgroundFlushCommits calls AsyncProcess#submit
> AsyncProcess#submit tries to get the region location but doesn't remove the
> mutation from the write buffer. If it doesn't get the location the mutation
> is added to the error list.
> then HTable#backgroundFlushCommits takes all mutations from the error list
> and adds them to the write buffer list.
> This should result in two references to the same mutation being in the write
> buffer list twice. It's not a big deal as two of the same mutation being
> executed should be ideponent (unless the two puts are executed across ms
> boundaries.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
