From hdfs-issues-return-244300-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Nov 29 17:57: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 5031918066C for ; Thu, 29 Nov 2018 17:57:04 +0100 (CET) Received: (qmail 16937 invoked by uid 500); 29 Nov 2018 16:57: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 16926 invoked by uid 99); 29 Nov 2018 16:57:03 -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, 29 Nov 2018 16:57:03 +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 C0594D0AC1 for ; Thu, 29 Nov 2018 16:57: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-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HldD9QvPHqyX for ; Thu, 29 Nov 2018 16:57: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 17C6E5FE0A for ; Thu, 29 Nov 2018 16:57: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 81769E2072 for ; Thu, 29 Nov 2018 16:57: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 475CA24DD6 for ; Thu, 29 Nov 2018 16:57:00 +0000 (UTC) Date: Thu, 29 Nov 2018 16:57:00 +0000 (UTC) From: =?utf-8?Q?=C3=8D=C3=B1igo_Goiri_=28JIRA=29?= To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13443) RBF: Update mount table cache immediately after changing (add/update/remove) mount table entries. 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-13443?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1670= 3499#comment-16703499 ]=20 =C3=8D=C3=B1igo Goiri commented on HDFS-13443: ------------------------------------ I would like to get this one in before HDFS-14079 so we can get rid of the = inconsistency and test there as [~surendrasingh] mentioned. > RBF: Update mount table cache immediately after changing (add/update/remo= ve) mount table entries. > -------------------------------------------------------------------------= ------------------------ > > Key: HDFS-13443 > URL: https://issues.apache.org/jira/browse/HDFS-13443 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: fs > Reporter: Mohammad Arshad > Assignee: Mohammad Arshad > Priority: Major > Labels: RBF > Attachments: HDFS-13443-branch-2.001.patch, HDFS-13443-branch-2.0= 02.patch, HDFS-13443.001.patch, HDFS-13443.002.patch, HDFS-13443.003.patch,= HDFS-13443.004.patch, HDFS-13443.005.patch, HDFS-13443.006.patch, HDFS-134= 43.007.patch, HDFS-13443.008.patch, HDFS-13443.009.patch, HDFS-13443.010.pa= tch, HDFS-13443.011.patch > > > Currently mount table cache is updated periodically, by default cache is = updated every minute. After change in mount table, user operations may stil= l use old mount table. This is bit wrong. > To update mount table cache, maybe we can do following > * *Add refresh API in MountTableManager which will update mount table ca= che.* > * *When there is a change in mount table entries, router admin server ca= n update its cache and ask other routers to update their cache*. For exampl= e if there are three routers R1,R2,R3 in a cluster then add mount table ent= ry API, at admin server side, will perform following sequence of action > ## user submit add mount table entry request on R1 > ## R1 adds the mount table entry in state store > ## R1 call refresh API on R2 > ## R1 calls refresh API on R3 > ## R1 directly freshest its cache > ## Add mount table entry response send back to user. -- 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