[ https://issues.apache.org/jira/browse/HBASE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997677#comment-15997677 ]
Lars Hofhansl commented on HBASE-17489: --------------------------------------- Hey [~Apache9]. Quick question: It seems that now we only set the scanner id in the ScanResponse when we actually created a new region scanner (but not on next or close). Is that by design? There is a problem with this now with OpenTSBD (well AsyncHBase) which ties requests and responses together using the scanner id. > ClientScanner may send a next request to a RegionScanner which has been > exhausted > --------------------------------------------------------------------------------- > > Key: HBASE-17489 > URL: https://issues.apache.org/jira/browse/HBASE-17489 > Project: HBase > Issue Type: Bug > Components: Client, scan > Affects Versions: 2.0.0, 1.3.0, 1.4.0 > Reporter: Duo Zhang > Assignee: Duo Zhang > Priority: Critical > Fix For: 2.0.0, 1.4.0, 1.3.1 > > Attachments: HBASE-17489-branch-1.3.patch, > HBASE-17489-branch-1.patch, HBASE-17489.patch, HBASE-17489-v1.patch, > HBASE-17489-v2.patch, HBASE-17489-v3.patch, HBASE-17489-v4.patch, > HBASE-17489-v4.patch, HBASE-17489-v5.patch, HBASE-17489-v6.patch > > > Found it when implementing HBASE-17045. Seems the final result of the scan is > correct but no doubt the logic is broken. We need to fix it to stop things > get worse in the future. -- This message was sent by Atlassian JIRA (v6.3.15#6346)