hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hung (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12825) Log slow name resolutions
Date Tue, 30 May 2017 22:24:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030259#comment-16030259
] 

Jonathan Hung commented on HADOOP-12825:
----------------------------------------

Btw, there was a "conflict", when applying to branch-2.7 it couldn't find the {{import javax.annotation.Nullable;}}
line, which is why I added a separate patch. Otherwise it applies cleanly.

> 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
>             Fix For: 2.8.0, 2.7.2, 3.0.0-alpha1
>
>         Attachments: getByName-call-graph.txt, HADOOP-12825.001.patch, HADOOP-12825.002.patch,
HADOOP-12825-branch-2.7.001.patch
>
>
> 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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message