hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koji Noguchi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-870) Topology is permanently cached
Date Thu, 25 Feb 2010 23:00:29 GMT

    [ https://issues.apache.org/jira/browse/HDFS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838583#action_12838583

Koji Noguchi commented on HDFS-870:

If we're going to add this, please make it optional.
Without HADOOP:5059, Namenode would hang 2-3 seconds for each expired/new datanode when it
calls topology script in our environment.
(or you can use java topology code)

It's ok at start up time since heap is relatively small and namenode is usually not out of
the safemode.

> Topology is permanently cached
> ------------------------------
>                 Key: HDFS-870
>                 URL: https://issues.apache.org/jira/browse/HDFS-870
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
> Replacing the topology script requires a namenode bounce because the NN caches the information
permanently.  It should really either expire it periodically or expire on -refreshNodes.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message