[
https://issues.apache.org/jira/browse/HBASE-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972172#comment-14972172
]
Enis Soztutar commented on HBASE-14687:
---------------------------------------
Yeah, since AP belongs to the connection, I think it was the reason that BM is
thread safe and shared from different threads. So the plan is to keep BM thread
safe and reduce internal synchronization? As long as we clearly document the
intended use pattern it is good. The example for BM uses it from multiple
threads.
> Un-synchronize BufferedMutator
> ------------------------------
>
> Key: HBASE-14687
> URL: https://issues.apache.org/jira/browse/HBASE-14687
> Project: HBase
> Issue Type: Bug
> Components: Client, Performance
> Reporter: Elliott Clark
> Assignee: Elliott Clark
>
> It should totally be possible to make BufferedMutatorImpl not use much ( if
> any ) locking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
