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 E063A200C81 for ; Fri, 26 May 2017 09:18:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DEE3C160BD9; Fri, 26 May 2017 07:18:08 +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 2CA19160BB8 for ; Fri, 26 May 2017 09:18:08 +0200 (CEST) Received: (qmail 5046 invoked by uid 500); 26 May 2017 07:18:07 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 5033 invoked by uid 99); 26 May 2017 07:18:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 May 2017 07:18:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 95C56CCF2A for ; Fri, 26 May 2017 07:18:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3IY24bUOBE8w for ; Fri, 26 May 2017 07:18: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 5B1765F2FD for ; Fri, 26 May 2017 07:18: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 94F56E0A75 for ; Fri, 26 May 2017 07:18: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 4C31321B57 for ; Fri, 26 May 2017 07:18:04 +0000 (UTC) Date: Fri, 26 May 2017 07:18:04 +0000 (UTC) From: "Phil Yang (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-18121) Scanner id should be reset when ScannerCallable reload the location MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 26 May 2017 07:18:09 -0000 Phil Yang created HBASE-18121: --------------------------------- Summary: Scanner id should be reset when ScannerCallable reload the location Key: HBASE-18121 URL: https://issues.apache.org/jira/browse/HBASE-18121 Project: HBase Issue Type: Bug Reporter: Phil Yang Assignee: Phil Yang If a scan rpc request failed, the RetryingCallable will retry by reload=true and may change the location because there may be a region movement. However, the ScannerCallable will still use the previous scanner id and send to the new server. In new RS the scanner id is not related with the old RS. The most possible result is UnknowScannerException and client will retry and there will be one useless rpc. And there is a low probability that there is a scanner with same id in the new RS, the result will be totally wrong. -- This message was sent by Atlassian JIRA (v6.3.15#6346)