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] [Updated] (HBASE-13926) Close the scanner only after Call#setResponse
Date Sat, 20 Jun 2015 05:21:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Anoop Sam John updated HBASE-13926:
    Hadoop Flags: Reviewed
          Status: Patch Available  (was: Open)

> Close the scanner only after Call#setResponse
> ---------------------------------------------
>                 Key: HBASE-13926
>                 URL: https://issues.apache.org/jira/browse/HBASE-13926
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver, Scanners
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>         Attachments: HBASE-13926.patch, HBASE-13926_V2.patch, HBASE-13926_V2.patch
> This is for HBASE-12295. We will be delivering cells directly from shared cache memory.
HBASE-12295 adds a ref count based prevention mechanism to avoid block eviction, when that
memory area in use by scanners. We will decrement ref count at scanner close. The memory area
will be in use till a cellblock is created or PB scan reply message is built. So we can delay
the close of the scanner until the response is set for the scanner Call. This is done via
a RpcCallback way. The callback is set on Call at scan time. Once the setResponse is done,
the Call will execute the RpcCallback.
> This jira also adds a facility to do some cleanup/close during the course of scan. Scan
from client makes many RPCs fetching N rows each time. Only at the end the scanner close will
happen. We will add a new batchClose() facility with which we can do any cleanup after every
rpc call is executed and rows fetched for return.

This message was sent by Atlassian JIRA

View raw message