[ 
https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627586#comment-14627586
 ] 

Anoop Sam John commented on HBASE-12295:
----------------------------------------

Just adding to what Ram said abt diff Cell impl

Write path 
-----------
KeyValue  and NoTagsKeyValue

Read path
----------
SizeCachedKeyValue, SizeCachedNoTagsKeyValue
OffheapCell, OffheapNoTagsCell  (this will be having size cached and it will be 
extending ByteBufferedCell  and also will be marked as Shared memory using the 
new interface)
DBE was/is having an impl already (ClonedSeekerState)  We will add one more 
counterpart for this which will be offheap backed - We need a rename. 
ClonedSeekerState does not look like a Cell at all
Prefix tree was/is having an impl already (ClonedPrefixCell) - We will add one 
more counterpart for this which will be offheap backed - We need a rename?

also read path will have KeyOnlyKeyValue stuff as well as the FakeCell impls 
for FirstOnROw, LastOnRow etc.

> 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_1.patch, HBASE-12295_1.pdf, 
> HBASE-12295_10.patch, HBASE-12295_12.patch, HBASE-12295_2.patch, 
> HBASE-12295_4.patch, HBASE-12295_4.pdf, HBASE-12295_5.pdf, 
> HBASE-12295_9.patch, 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)

Reply via email to