From hdfs-issues-return-253138-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Feb 25 23:43:04 2019 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 0B412180626 for ; Tue, 26 Feb 2019 00:43:03 +0100 (CET) Received: (qmail 10377 invoked by uid 500); 25 Feb 2019 23:43:03 -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 10366 invoked by uid 99); 25 Feb 2019 23:43:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2019 23:43:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 69E84C198D for ; Mon, 25 Feb 2019 23:43:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id OXC44cVOJfAh for ; Mon, 25 Feb 2019 23:43:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id ED831623C6 for ; Mon, 25 Feb 2019 23:43:00 +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 78F03E01AC for ; Mon, 25 Feb 2019 23:43: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 3D6D524558 for ; Mon, 25 Feb 2019 23:43:00 +0000 (UTC) Date: Mon, 25 Feb 2019 23:43:00 +0000 (UTC) From: "Erik Krogen (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-14272) [SBN read] ObserverReadProxyProvider should sync with active txnID on startup 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-14272?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1677= 7406#comment-16777406 ]=20 Erik Krogen commented on HDFS-14272: ------------------------------------ [~shv]: {code} Since proxies to individual NNs have not been created yet, changeProxy() wi= ll create proxy for the corresponding NN, then call getHAServiceState() and= cache the state. Then it will proceed with the msync() call, which is not = needed because the client already knows the state of that NN. {code} Yes, the {{changeProxy()}} within ORPP will call {{getHAServiceState()}}. I= f an {{msync()}} was subsequently sent over this proxy, I agree it would be= somewhat redundant. However, {{msync()}} is called on the {{failoverProxy}= }, which is a CFPP. The {{changeProxy()}} method on CFPP will _not_ call {{= getHAServiceState()}}; the {{msync()}} method is the first call that is per= formed on the proxy. Thus the number of RPC calls is identical. Whether tho= se RPCs are calls to {{getHAServiceState()}} or {{msync()}} is not importan= t for performance, and re-using the {{msync()}} functionality is cleaner IM= O. [~csun]: thanks for the comments, I uploaded v002 addressing them. > [SBN read] ObserverReadProxyProvider should sync with active txnID on sta= rtup > -------------------------------------------------------------------------= ---- > > Key: HDFS-14272 > URL: https://issues.apache.org/jira/browse/HDFS-14272 > Project: Hadoop HDFS > Issue Type: Bug > Components: tools > Environment: CDH6.1 (Hadoop 3.0.x) + Consistency Reads from Stand= by + SSL + Kerberos + RPC encryption > Reporter: Wei-Chiu Chuang > Assignee: Erik Krogen > Priority: Major > Attachments: HDFS-14272.000.patch, HDFS-14272.001.patch, HDFS-142= 72.002.patch > > > It is typical for integration tests to create some files and then check= =C2=A0their existence. For example, like the following simple bash script: > {code:java} > # hdfs dfs -touchz /tmp/abc > # hdfs dfs -ls /tmp/abc > {code} > The test executes HDFS bash command sequentially, but it may fail with Co= nsistent Standby Read because the -ls=C2=A0does not find the file. > Analysis: the second bash command, while launched sequentially after the = first one, is not aware of the state id returned from the first bash comman= d. So ObserverNode wouldn't wait for the the edits to get propagated, and t= hus fails. > I've got a cluster where the Observer has tens of seconds of RPC latency,= and this becomes very annoying. (I am still trying to figure out why this = Observer has such a long RPC latency. But that's another story.) -- 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