[
https://issues.apache.org/jira/browse/HBASE-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274495#comment-13274495
]
Anoop Sam John commented on HBASE-5974:
---------------------------------------
{quote}
Suppose client gets 'Bad cookie' notification from server in the middle of a
long scan.
If the client wants to continue where it left off in a new scanner (I assume
this is the default / desriable behavior), the client needs to remember the key
of the last KV it previously received and .
{quote}
Yes. The client knows the last row and based on this it can create a new
scanner so as to continue the scan from that point. This is already in place
and this what will happen when client gets a NSRE in the middle of the scan
from RS.
{quote}
But in faulty condition, I think the key of last KV would still be needed.
{quote}
Any specific reason in your mind Ted? As such I think a seq numbering is
enough...
> Scanner retry behavior with RPC timeout on next() seems incorrect
> -----------------------------------------------------------------
>
> Key: HBASE-5974
> URL: https://issues.apache.org/jira/browse/HBASE-5974
> Project: HBase
> Issue Type: Bug
> Components: client, regionserver
> Affects Versions: 0.90.7, 0.92.1, 0.94.0, 0.96.0
> Reporter: Todd Lipcon
> Priority: Critical
>
> I'm seeing the following behavior:
> - set RPC timeout to a short value
> - call next() for some batch of rows, big enough so the client times out
> before the result is returned
> - the HConnectionManager stuff will retry the next() call to the same server.
> At this point, one of two things can happen: 1) the previous next() call will
> still be processing, in which case you get a LeaseException, because it was
> removed from the map during the processing, or 2) the next() call will
> succeed but skip the prior batch of rows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
