[
https://issues.apache.org/jira/browse/HDFS-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478557#comment-13478557
]
Eli Collins commented on HDFS-3990:
-----------------------------------
Two small comments, +1 otherwise!
- Let's remove this line and leave peerHostName as null since we're claiming
the peerHostname is the "hostname from the actual connection". It's also useful
to have something to check to indicate the peerHostName has not been
determined.
{code}this.peerHostName = hostName; // will assume it's the given host for
now{code}
- move the "// Update the IP to the address of the RPC request..." comment up
with the setIpAddr call
> NN's health report has severe performance problems
> --------------------------------------------------
>
> Key: HDFS-3990
> URL: https://issues.apache.org/jira/browse/HDFS-3990
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HDFS-3990.branch-0.23.patch, HDFS-3990.patch,
> HDFS-3990.patch, HDFS-3990.patch, HDFS-3990.patch, HDFS-3990.patch,
> HDFS-3990.patch, hdfs-3990.txt, hdfs-3990.txt
>
>
> The dfshealth page will place a read lock on the namespace while it does a
> dns lookup for every DN. On a multi-thousand node cluster, this often
> results in 10s+ load time for the health page. 10 concurrent requests were
> found to cause 7m+ load times during which time write operations blocked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
