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 CF6CD200D11 for ; Mon, 2 Oct 2017 22:50:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CDCFC160BCB; Mon, 2 Oct 2017 20:50:08 +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 206DA1609C0 for ; Mon, 2 Oct 2017 22:50:07 +0200 (CEST) Received: (qmail 57278 invoked by uid 500); 2 Oct 2017 20:50:07 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 57267 invoked by uid 99); 2 Oct 2017 20:50:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2017 20:50:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 680DA199FF8 for ; Mon, 2 Oct 2017 20:50:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id VDBABCAFJH5o for ; Mon, 2 Oct 2017 20:50:05 +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 764705FB57 for ; Mon, 2 Oct 2017 20:50:05 +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 D9AE4E0536 for ; Mon, 2 Oct 2017 20:50:03 +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 A8F0C242B4 for ; Mon, 2 Oct 2017 20:50:02 +0000 (UTC) Date: Mon, 2 Oct 2017 20:50:02 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14921) Conflicts when starting daemons with the same name 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 20:50:09 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14921?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 188799#comment-16188799 ]=20 Allen Wittenauer commented on HADOOP-14921: ------------------------------------------- A few thoughts: a) In production systems, the user part of the string likely won't be the s= ame, much less running on the same system. b) If people REALLY want to run the two daemons on the same node as the sam= e user, then HADOOP_IDENT_STRING is already available to provide a way for = users to do their own differentiation, just like they can with running e.g.= , two DataNode processes on the same node. c) Or, custom entries in hadoop-user-function to do exactly what you're pro= posing. =20 d) Having multiple, different daemons called the same thing is awful. jps,= logs, pids, documentation ... it's going to be terrible for admins. ("No, = I meant the YARN router." "No, I meant the HFDS router.") I'd HIGHLY recom= mend renaming it to something else. > Conflicts when starting daemons with the same name > -------------------------------------------------- > > Key: HADOOP-14921 > URL: https://issues.apache.org/jira/browse/HADOOP-14921 > Project: Hadoop Common > Issue Type: Bug > Reporter: =C3=8D=C3=B1igo Goiri > > HDFS-10467 is adding a {{Router}} while YARN already added one for YARN-2= 915. Both of them are ultimately started from {{hadoop-functions.sh}}. For = the PID file both of them end up using {{/tmp/hadoop-hadoop-router.pid}}. I= propose to use the command name also for the PID file. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org