[jira] [Issue Comment Deleted] (HBASE-16296) Reverse scan performance degrades when scanner cache size matches page filter size

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl updated HBASE-16296:
----------------------------------
    Comment: was deleted

(was: OK. I find it about 10ms, unless I set the caching to 5, in which case it takes about 150ms.
(I did run the data loader script and flushed the table)
)

> 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: 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)