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 512D0200C77 for ; Mon, 1 May 2017 18:52:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4FBA3160BA0; Mon, 1 May 2017 16:52:10 +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 97978160BAE for ; Mon, 1 May 2017 18:52:09 +0200 (CEST) Received: (qmail 95346 invoked by uid 500); 1 May 2017 16:52: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 95155 invoked by uid 99); 1 May 2017 16:52:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 May 2017 16:52:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A7D0C1B1433 for ; Mon, 1 May 2017 16:52:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id utA1GJJn51GX for ; Mon, 1 May 2017 16:52: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 3C89D5FE56 for ; Mon, 1 May 2017 16:52:06 +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 49960E06CF for ; Mon, 1 May 2017 16:52:05 +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 693C221DEC for ; Mon, 1 May 2017 16:52:04 +0000 (UTC) Date: Mon, 1 May 2017 16:52:04 +0000 (UTC) From: "Josh Elser (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17534) SecureBulkLoadClient squashes DoNotRetryIOExceptions from the server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 01 May 2017 16:52:10 -0000 [ https://issues.apache.org/jira/browse/HBASE-17534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-17534: ------------------------------- Attachment: HBASE-17534.004.branch-1.patch .004 Same as .003, just retriggering hadoop-qa since it's been 2months > SecureBulkLoadClient squashes DoNotRetryIOExceptions from the server > -------------------------------------------------------------------- > > Key: HBASE-17534 > URL: https://issues.apache.org/jira/browse/HBASE-17534 > Project: HBase > Issue Type: Bug > Components: Client > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 1.4.0, 1.2.6, 1.3.2, 1.1.11 > > Attachments: HBASE-17534.001.branch-1.patch, HBASE-17534.002.branch-1.patch, HBASE-17534.003.branch-1.patch, HBASE-17534.004.branch-1.patch > > > While writing some tests against 1.x, I noticed that what should have been a DoNotRetryIOException sent to the client from a RegionServer was getting retried until it reached the hbase client retries limit. > Upon inspection, I found that the SecureBulkLoadClient was wrapping all Exceptions from the RPC as an IOException. I believe this is creating a case where the RPC system doesn't notice that there's a DNRIOException wrapped beneath it, thinking it's a transient error. > This results in clients having to wait for the retry limit to be reached before they get acknowledgement that something failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)