From hdfs-issues-return-219812-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu May 10 13:59:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D8FB018063A for ; Thu, 10 May 2018 13:59:03 +0200 (CEST) Received: (qmail 27537 invoked by uid 500); 10 May 2018 11:59:02 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 27526 invoked by uid 99); 10 May 2018 11:59:02 -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; Thu, 10 May 2018 11:59:02 +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 434B3C6FAA for ; Thu, 10 May 2018 11:59:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, 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 Ng_kvM2vppkH for ; Thu, 10 May 2018 11:59:01 +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 49C1C5F1ED for ; Thu, 10 May 2018 11:59:01 +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 7C616E0F31 for ; Thu, 10 May 2018 11:59:00 +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 44DF021546 for ; Thu, 10 May 2018 11:59:00 +0000 (UTC) Date: Thu, 10 May 2018 11:59:00 +0000 (UTC) From: "Bibin A Chundatt (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13388) RequestHedgingProxyProvider calls multiple configured NNs all the time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-13388?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1647= 0293#comment-16470293 ]=20 Bibin A Chundatt commented on HDFS-13388: ----------------------------------------- Since HDFS-12813 is long back closed might need a backport jira . I am ok w= ith you filing jira too. > RequestHedgingProxyProvider calls multiple configured NNs all the time > ---------------------------------------------------------------------- > > Key: HDFS-13388 > URL: https://issues.apache.org/jira/browse/HDFS-13388 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs-client > Reporter: Jinglun > Assignee: Jinglun > Priority: Major > Fix For: 3.2.0, 3.1.1, 3.0.3 > > Attachments: HADOOP-13388.0001.patch, HADOOP-13388.0002.patch, HA= DOOP-13388.0003.patch, HADOOP-13388.0004.patch, HADOOP-13388.0005.patch, HA= DOOP-13388.0006.patch, HADOOP-13388.0007.patch, HADOOP-13388.0008.patch, HA= DOOP-13388.0009.patch, HADOOP-13388.0010.patch, HADOOP-13388.0011.patch, HA= DOOP-13388.0012.patch, HADOOP-13388.0013.patch, HADOOP-13388.0014.patch > > > In HDFS-7858 RequestHedgingProxyProvider was designed to "first simultane= ously call multiple configured NNs to decide which is the active Namenode a= nd then for subsequent calls it will invoke the previously successful NN ."= But the current code call multiple configured NNs every time even when we = already got the successful NN.=20 > That's because in RetryInvocationHandler.java, ProxyDescriptor's member = proxyInfo is assigned only when it is constructed or when failover occurs. = RequestHedgingProxyProvider.currentUsedProxy is null in both cases, so the = only proxy we can get is always a dynamic proxy handled by RequestHedgingIn= vocationHandler.class.=C2=A0RequestHedgingInvocationHandler.class handles i= nvoked method by calling multiple configured NNs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org