[
https://issues.apache.org/jira/browse/HBASE-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811493#comment-15811493
]
ramkrishna.s.vasudevan commented on HBASE-17434:
------------------------------------------------
So in this patch if applied on top of HBASE-17081 - will work with the
assumption that even when we do getScanners() and got the readOnly copy -
either the current active is not in the pipeline or it may be in the pipeline.
It could also be that after the getSegments() was done by getScanners() the
'active' got reset to a new one but still we assume it is fine?
And more importantly all the operations in getScanners() in HBASE-17081 will be
done on the readOnlyCopy?
> New Synchronization Scheme for Compaction Pipeline
> --------------------------------------------------
>
> Key: HBASE-17434
> URL: https://issues.apache.org/jira/browse/HBASE-17434
> Project: HBase
> Issue Type: Bug
> Reporter: Eshcar Hillel
> Assignee: Eshcar Hillel
> Attachments: HBASE-17434-V01.patch, HBASE-17434-V02.patch,
> HBASE-17434-V03.patch
>
>
> A new copyOnWrite synchronization scheme is introduced for the compaction
> pipeline.
> The new scheme is better since it removes the lock from getSegments() which
> is invoked in every get and scan operation, and it reduces the number of
> LinkedList objects that are created at runtime, thus can reduce GC (not by
> much, but still...).
> In addition, it fixes the method getTailSize() in compaction pipeline. This
> method creates a MemstoreSize object which comprises the data size and the
> overhead size of the segment and needs to be atomic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
