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 E1636200D11 for ; Mon, 2 Oct 2017 23:33:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DFD50160BCB; Mon, 2 Oct 2017 21:33:06 +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 316751609C0 for ; Mon, 2 Oct 2017 23:33:06 +0200 (CEST) Received: (qmail 82869 invoked by uid 500); 2 Oct 2017 21:33:05 -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 82856 invoked by uid 99); 2 Oct 2017 21:33:05 -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; Mon, 02 Oct 2017 21:33:05 +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 7362BD03A7 for ; Mon, 2 Oct 2017 21:33:03 +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-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 NB2AiIVGY_nr for ; Mon, 2 Oct 2017 21:33:02 +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 A03895F6C3 for ; Mon, 2 Oct 2017 21:33:02 +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 28057E04F4 for ; Mon, 2 Oct 2017 21:33:02 +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 DBB83242B3 for ; Mon, 2 Oct 2017 21:33:01 +0000 (UTC) Date: Mon, 2 Oct 2017 21:33:01 +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-12577) Rename Router tooling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 02 Oct 2017 21:33:07 -0000 [ https://issues.apache.org/jira/browse/HDFS-12577?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1618= 8880#comment-16188880 ]=20 =C3=8D=C3=B1igo Goiri commented on HDFS-12577: ------------------------------------ For the last few months, we've been getting feedback about the naming issue= s. I'd like to use this JIRA to cover these. I'd like to summarize the different comments: * [~zhz] and [~shv] were concerned about distinguishing it from regular HDF= S federation. * [~manojg] similarly thought the command line to manage the mount table co= uld get confusing as it currently used {{hdfs federation}}.. * [~aw] brought up the confusion of having two daemons (in YARN and HDFS) c= alled {{Router}}. From this feedback, I propose the following: * Referring to this effort as "Router-Based Federation" or RBF. * Create a class called {{HdfsRouter}} to start the Router, so the current = main from Router would move here. The command would still be {{hdfs router}= } but it would start {{HdfsRouter}} and avoid conflicts when calling {{jps}= } etc. * Rename the command I added for HDFS-10467 from {{hdfs federation}} to {{h= dfs routeradmin}}. Alternatively, I could merge both the Router start and t= he admin into {{hdfs router}} and call {{HdfsRouter}} and {{RouterAdmin}} i= nternally. Thoughts? > Rename Router tooling > --------------------- > > Key: HDFS-12577 > URL: https://issues.apache.org/jira/browse/HDFS-12577 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: fs > Reporter: =C3=8D=C3=B1igo Goiri > Fix For: HDFS-10467 > > > Currently the naming for Router Based Federation has a couple conflicts: > * Both YARN and HDFS have a Router component which may cause issues for t= he PID file and JPS. > * The tool to manage the mount table is called using {{hdfs federation}}.= This may cause confusion with the regular HDFS federation. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org