Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E90D619E60 for ; Sun, 28 Feb 2016 21:00:19 +0000 (UTC) Received: (qmail 1248 invoked by uid 500); 28 Feb 2016 21:00:19 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 1194 invoked by uid 500); 28 Feb 2016 21:00:19 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 1172 invoked by uid 99); 28 Feb 2016 21:00:19 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Feb 2016 21:00:19 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7DDE72C1F64 for ; Sun, 28 Feb 2016 21:00:19 +0000 (UTC) Date: Sun, 28 Feb 2016 21:00:19 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-12825) Log slow name resolutions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171183#comment-15171183 ] Chris Nauroth commented on HADOOP-12825: ---------------------------------------- I see in git log that this patch has been committed to trunk, branch-2 and branch-2.8. Can we resolve the issue, or is there some other work remaining? > Log slow name resolutions > -------------------------- > > Key: HADOOP-12825 > URL: https://issues.apache.org/jira/browse/HADOOP-12825 > Project: Hadoop Common > Issue Type: Improvement > Reporter: Sidharta Seethana > Assignee: Sidharta Seethana > Attachments: HADOOP-12825.001.patch, HADOOP-12825.002.patch, getByName-call-graph.txt > > > Logging slow name resolutions would be useful in identifying DNS performance issues in a cluster. Most resolutions go through {{org.apache.hadoop.security.SecurityUtil.getByName}} ( see attached call graph ). Adding additional logging to this method would expose such issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)