[
https://issues.apache.org/jira/browse/HBASE-15378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182573#comment-15182573
]
ramkrishna.s.vasudevan commented on HBASE-15378:
------------------------------------------------
So the case here is that there are no results and also the TIME_LIMIT has
reached but still we try to handle it as heartBeatMessage and the ClientScanner
does not handle this case.
So here
{code}
while ((callable != null && callable.isHeartbeatMessage())
531 || (doneWithRegion(remainingResultSize, countdown,
serverHasMoreResults)
532 && (!partialResults.isEmpty() || possiblyNextScanner(countdown,
values == null))));
{code}
On seeing it is a heartBeatMessage you will once again continue the loop? I
think am missing something here.
> Scanner can not handle a heartbeat message with no results
> ----------------------------------------------------------
>
> Key: HBASE-15378
> URL: https://issues.apache.org/jira/browse/HBASE-15378
> Project: HBase
> Issue Type: Bug
> Components: dataloss, Scanners
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Phil Yang
> Assignee: Phil Yang
> Priority: Critical
> Attachments: HBASE-15378-v1.txt, HBASE-15378-v2.txt,
> HBASE-15378-v3.txt
>
>
> When a RS scanner get a TIME_LIMIT_REACHED_MID_ROW state, they will stop
> scanning and send back what it has read to client and mark the message as a
> heartbeat message. If there is no cell has been read, it will be an empty
> response.
> However, ClientScanner only handles the situation that the client gets an
> empty heartbeat and its cache is not empty. If the cache is empty too, it
> will be regarded as end-of-region and open a new scanner for next region.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
