[
https://issues.apache.org/jira/browse/HBASE-21032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577500#comment-16577500
]
Xu Cang commented on HBASE-21032:
---------------------------------
[~timoha]
this is caused by HBASE-20457. This patch set read type to *STREAM* when a
limit is reached. (patch applied to 2.1.0 but 2.0.0)
#checkTimeLimit will always return true after this since "returnImmediately" is
set to true.
> ScanResponses contain only one cell each
> ----------------------------------------
>
> Key: HBASE-21032
> URL: https://issues.apache.org/jira/browse/HBASE-21032
> Project: HBase
> Issue Type: Bug
> Components: Scanners
> Affects Versions: 2.1.0
> Environment: HBase 2.1.0
> Hadoop 2.8.4
> Java 8
> Reporter: Andrey Elenskiy
> Priority: Major
> Attachments: App.java
>
>
> I have a long row with a bunch of columns that I'm scanning with
> setAllowPartialResults(true). In the response I'm getting the first partial
> ScanResponse being around 2MB with multiple cells while all of the consequent
> ones being 1 cell per ScanResponse. After digging more, I found that each of
> those single cell ScanResponse partials are preceded by a heartbeat (zero
> cells). This results in two requests per cell to a regionserver.
> I've attached code to reproduce it on hbase version 2.1.0 (it works as
> expected on 2.0.0 and 2.0.1).
> [^App.java]
> I'm fairly certain it's a serverside issue as
> [gohbase|https://github.com/tsuna/gohbase] client is having the same issue. I
> have not tried to reproduce this with multi-row scan.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
