hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18055) HBASE-17917 closes the scanners while a scan is in progess for switching over to stream reads
Date Tue, 16 May 2017 06:59:04 GMT

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

Anoop Sam John commented on HBASE-18055:

Here the issue is the results is not yet serialized back to client. They refer to the blocks
which where there in L2 cache.  Before sending reply back, the scanner seems closed and that
was reducing the ref count and possibly making the ref count to 0 and evictions.

> HBASE-17917 closes the scanners while a scan is in progess for switching over to stream
> ---------------------------------------------------------------------------------------------
>                 Key: HBASE-18055
>                 URL: https://issues.apache.org/jira/browse/HBASE-18055
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver, Scanners
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0
> In HBASE-17917 tries to switch from pread to stream read when a specific size of bytes
are read. So in order to switch over, it closes the existing scanners and creates a new scanners
with pread=false.
> When we close the exisitng scanners - if the blocks are served from offheap cache we
will decrement the ref count on those blocks and if it becomes zero we make the block ready
for eviction. Then there is a chance that the result could be corrupted if new blocks occupy
the cache. So the expectation was that till the RPC call completes the response we will hold
on to the blocks that are referred by the scan. (except the last one). So trying to switch
over to stream read will break this expectation and hence TestBlockEvictionfromclient fails.

This message was sent by Atlassian JIRA

View raw message