[
https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570334#comment-14570334
]
ramkrishna.s.vasudevan commented on HBASE-12295:
------------------------------------------------
Given that we can solve this without using Result we could continue the way we
handle with scanners and scanners doing the ref counting part.
I would any way think that if we use Result, may be we need not increment every
cell coming from that block. Per block used in the result we can increment the
count.
But doing anything with Result would need to have a Server side result object
that may do some extra APIs/methods to handle these return/close stuff.
As Stack points out
bq.I would say that the creation of the CellBlock in memory is something we
would like to get away from some day.
If this has to happen then its better we handle things with the Result - but
incrementing the ref count for every cell in the block may be we can see if
there is another way.
For now we are not handling this through Result and handling things using
CellBlock and existing scanners.
> Prevent block eviction under us if reads are in progress from the BBs
> ---------------------------------------------------------------------
>
> Key: HBASE-12295
> URL: https://issues.apache.org/jira/browse/HBASE-12295
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
> Attachments: HBASE-12295.pdf, HBASE-12295_trunk.patch
>
>
> While we try to serve the reads from the BBs directly from the block cache,
> we need to ensure that the blocks does not get evicted under us while
> reading. This JIRA is to discuss and implement a strategy for the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
