From issues-return-149311-archive-asf-public=cust-asf.ponee.io@flink.apache.org Wed Jan 24 14:20:14 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 630AA180630 for ; Wed, 24 Jan 2018 14:20:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 50D53160C3C; Wed, 24 Jan 2018 13:20:14 +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 95B02160C2E for ; Wed, 24 Jan 2018 14:20:13 +0100 (CET) Received: (qmail 87813 invoked by uid 500); 24 Jan 2018 13:20:12 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 87804 invoked by uid 99); 24 Jan 2018 13:20:12 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2018 13:20:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 39A2D1A01A1 for ; Wed, 24 Jan 2018 13:20:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id TiERPKqQw-7p for ; Wed, 24 Jan 2018 13:20:11 +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 D6DD95FB20 for ; Wed, 24 Jan 2018 13:20:09 +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 0121FE0662 for ; Wed, 24 Jan 2018 13:20:08 +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 9D3F2240F2 for ; Wed, 24 Jan 2018 13:20:02 +0000 (UTC) Date: Wed, 24 Jan 2018 13:20:02 +0000 (UTC) From: "Chesnay Schepler (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (FLINK-8445) hostname used in metric names for taskmanager and jobmanager are not consistent 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/FLINK-8445?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Chesnay Schepler closed FLINK-8445. ----------------------------------- > hostname used in metric names for taskmanager and jobmanager are not cons= istent > -------------------------------------------------------------------------= ------ > > Key: FLINK-8445 > URL: https://issues.apache.org/jira/browse/FLINK-8445 > Project: Flink > Issue Type: Bug > Components: Metrics > Affects Versions: 1.3.1, 1.4.0 > Environment: I think that this problem is present for metrics rep= orting enabled configurations that include '' as part of the scope fo= r the metrics.=C2=A0 For example, using Graphite reporting configuration in= flink-conf.yaml below: > {code:java} > metrics.scope.jm: flink..jobmanager > metrics.scope.jm.job: flink..jobmanager. > metrics.scope.tm: flink..taskmanager > metrics.scope.tm.job: flink..taskmanager. > metrics.scope.task: flink..taskmanager... > metrics.scope.operator: flink..taskmanager... > metrics.reporters: graphite > metrics.reporter.graphite.class: org.apache.flink.metrics.graphite.Graphi= teReporter > ...{code} > Reporter: Chris Thomson > Priority: Minor > > Enabled Flink metrics reporting using Graphite using system scopes that c= ontain '' for both the job manager and task manager.=C2=A0 The result= ing metrics reported to Graphite use two different representations for ''. > For *Task Manager metrics*=C2=A0it uses the *short hostname*=C2=A0(withou= t the DNS domain).=C2=A0 This is a result of logic in org.apache.flink.runt= ime.taskmanager.TaskManagerLocation constructor that tries to extract the s= hort hostname from the fully qualified domain name looked up from InetAddre= ss.getCanonicalHostName(). > For *Job Manager metrics*=C2=A0it uses the *fully qualified domain name*= =C2=A0(with the DNS domain). This is a result of there being no logic in or= g.apache.flink.runtime.jobmanager.JobManagerRunner or org.apache.flink.runt= ime.rpc.akka.AkkaRpcService to perform equivalent normalization of the full= y qualified domain name down to the short hostname. > Ideally the '' placeholders in the system scopes for the job manage= r and task manager related metrics would be replaced with a consistent valu= e (either the short hostname or the fully qualified domain name).=C2=A0 Eve= n better if there was a configuration option to decide which one should be = used for metric name generation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)