hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16296) Reverse scan performance degrades when scanner cache size matches page filter size
Date Mon, 01 Aug 2016 14:48:20 GMT

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

Sean Busbey commented on HBASE-16296:
-------------------------------------

I'd rather a release note / known issue calling out the edge case where things fall over than
change behavior in a maintenance release, but I don't have time to review the specifics of
this case and I trust y'all to make a call on the tradeoff wrt severity.

> Reverse scan performance degrades when scanner cache size matches page filter size
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-16296
>                 URL: https://issues.apache.org/jira/browse/HBASE-16296
>             Project: HBase
>          Issue Type: Bug
>            Reporter: James Taylor
>         Attachments: 16296-MAYBE-v2.txt, 16296-MAYBE.txt, PAgefilter.patch, generatedata-snippet.java,
repro-snippet.java
>
>
> When a reverse scan is done, the server seems to not know it's done when the scanner
cache size matches the number of rows in a PageFilter. See PHOENIX-3121 for how this manifests
itself. We have a standalone, pure HBase API reproducer too that I'll attach (courtesy of
[~churromorales] and [~mujtabachohan]).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message