[
https://issues.apache.org/jira/browse/HBASE-12748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311549#comment-14311549
]
Lars Hofhansl commented on HBASE-12748:
---------------------------------------
How about just using an ArrayList via an AtomicReference (or volatile
reference) and keep it sorted correctly?
Each time we add a coprocessor we'd clone and re-sort the list, but that would
be rare.
> RegionCoprocessorHost.execOperation creates too many iterator objects
> ---------------------------------------------------------------------
>
> Key: HBASE-12748
> URL: https://issues.apache.org/jira/browse/HBASE-12748
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 0.94.25, 0.98.9
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Fix For: 2.0.0, 1.0.1, 0.94.27, 0.98.11
>
> Attachments: HBase-12748.patch
>
>
> This is typical pattern of enhanced for ... loop usage in a hot code path.
> For every HBase operation it instantiates iterator for coprocessor list
> twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
