From issues-return-40914-archive-asf-public=cust-asf.ponee.io@tez.apache.org Tue Nov 5 14:00:11 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id EA267180648 for ; Tue, 5 Nov 2019 15:00:10 +0100 (CET) Received: (qmail 37575 invoked by uid 500); 5 Nov 2019 14:00:10 -0000 Mailing-List: contact issues-help@tez.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tez.apache.org Delivered-To: mailing list issues@tez.apache.org Received: (qmail 37564 invoked by uid 99); 5 Nov 2019 14:00:10 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2019 14:00:10 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 71A7EE2DF0 for ; Tue, 5 Nov 2019 14:00:09 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id DEF3178077D for ; Tue, 5 Nov 2019 14:00:08 +0000 (UTC) Date: Tue, 5 Nov 2019 14:00:08 +0000 (UTC) From: =?utf-8?Q?L=C3=A1szl=C3=B3_Bodor_=28Jira=29?= To: issues@tez.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (TEZ-4097) Report localHostname in Fetcher failure log messages 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/TEZ-4097?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] L=C3=A1szl=C3=B3 Bodor updated TEZ-4097: ------------------------------ Description:=20 Currently, a fetch failure is reported like this: {code} 2019-11-05 02:50:35,972 [WARN] [Fetcher_B {Map_4} #1] |shuffle.Fetcher|: Fe= tch Failure from host while connecting: other_host, attempt: InputAttemptId= entifier [inputIdentifier=3D1, attemptNumber=3D0, pathComponent=3Dattempt_1= 572936153637_0005_1_00_000000_0_10003, spillType=3D0, spillId=3D-1] Informi= ng ShuffleManager: java.net.SocketTimeoutException: Read timed out ... {code} For debugging network/ssl/etc. issues on cluster, it would be convenient to= see the local host's name in these messages (which is present in the fetch= er as localHostname property), as in the logs collected by yarn cli, it's n= ot obvious for the first sight. The same applies to FetcherOrderedGrouped, which reports something like: {code} 2019-11-05 03:13:11,046 [WARN] [Fetcher_O {Map_1} #0] |orderedgrouped.Fetch= erOrderedGrouped|: Failed to verify reply after connecting to other_host:13= 562 with 1 inputs pending javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorExcept= ion: PKIX path building failed: sun.security.provider.certpath.SunCertPathB= uilderException: unable to find valid certification path to requested targe= t {code} was: Currently, a fetch failure is reported like this: {code} 2019-11-05 02:50:35,972 [WARN] [Fetcher_B {Map_4} #1] |shuffle.Fetcher|: Fe= tch Failure from host while connecting: *other_host*, attempt: InputAttempt= Identifier [inputIdentifier=3D1, attemptNumber=3D0, pathComponent=3Dattempt= _1572936153637_0005_1_00_000000_0_10003, spillType=3D0, spillId=3D-1] Infor= ming ShuffleManager: java.net.SocketTimeoutException: Read timed out ... {code} For debugging network/ssl/etc. issues on cluster, it would be convenient to= see the local host's name in these messages (which is present in the fetch= er as localHostname property), as in the logs collected by yarn cli, it's n= ot obvious for the first sight. The same applies to FetcherOrderedGrouped, which reports something like: {code} 2019-11-05 03:13:11,046 [WARN] [Fetcher_O {Map_1} #0] |orderedgrouped.Fetch= erOrderedGrouped|: Failed to verify reply after connecting to rizhangdebug1= 0-2.gce.cloudera.com:13562 with 1 inputs pending javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorExcept= ion: PKIX path building failed: sun.security.provider.certpath.SunCertPathB= uilderException: unable to find valid certification path to requested targe= t {code} > Report localHostname in Fetcher failure log messages > ---------------------------------------------------- > > Key: TEZ-4097 > URL: https://issues.apache.org/jira/browse/TEZ-4097 > Project: Apache Tez > Issue Type: Improvement > Reporter: L=C3=A1szl=C3=B3 Bodor > Assignee: L=C3=A1szl=C3=B3 Bodor > Priority: Minor > > Currently, a fetch failure is reported like this: > {code} > 2019-11-05 02:50:35,972 [WARN] [Fetcher_B {Map_4} #1] |shuffle.Fetcher|: = Fetch Failure from host while connecting: other_host, attempt: InputAttempt= Identifier [inputIdentifier=3D1, attemptNumber=3D0, pathComponent=3Dattempt= _1572936153637_0005_1_00_000000_0_10003, spillType=3D0, spillId=3D-1] Infor= ming ShuffleManager: > java.net.SocketTimeoutException: Read timed out > ... > {code} > For debugging network/ssl/etc. issues on cluster, it would be convenient = to see the local host's name in these messages (which is present in the fet= cher as localHostname property), as in the logs collected by yarn cli, it's= not obvious for the first sight. > The same applies to FetcherOrderedGrouped, which reports something like: > {code} > 2019-11-05 03:13:11,046 [WARN] [Fetcher_O {Map_1} #0] |orderedgrouped.Fet= cherOrderedGrouped|: Failed to verify reply after connecting to other_host:= 13562 with 1 inputs pending > javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorExce= ption: PKIX path building failed: sun.security.provider.certpath.SunCertPat= hBuilderException: unable to find valid certification path to requested tar= get > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)