Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D6FB2200C79 for ; Fri, 5 May 2017 03:30:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D5D5C160BC5; Fri, 5 May 2017 01:30:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2F17E160BB0 for ; Fri, 5 May 2017 03:30:09 +0200 (CEST) Received: (qmail 47767 invoked by uid 500); 5 May 2017 01:30:08 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 47755 invoked by uid 99); 5 May 2017 01:30:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2017 01:30:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 055FA188A4D for ; Fri, 5 May 2017 01:30:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id A4lr_IMi9f6C for ; Fri, 5 May 2017 01:30:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 927925F5F9 for ; Fri, 5 May 2017 01:30:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E5816E0C13 for ; Fri, 5 May 2017 01:30:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4E2F621DF2 for ; Fri, 5 May 2017 01:30:04 +0000 (UTC) Date: Fri, 5 May 2017 01:30:04 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 05 May 2017 01:30:10 -0000 [ https://issues.apache.org/jira/browse/HBASE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997701#comment-15997701 ] Duo Zhang commented on HBASE-17489: ----------------------------------- Yeah in the hbase client we only use the scanner id when opening scanner since when calling next or close you need to send the scanner id to RS so you must have known the scanner id already... Mind openning a issue for this? I think it is easy to fix. We need to add some comments and also a UT to confirm that we do not remove it again in the future. Thanks. > 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)