You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2021/01/21 13:36:04 UTC
[jira] [Resolved] (HADOOP-8629) Add option for TableMapping to
reload mapping file on match failure
[ https://issues.apache.org/jira/browse/HADOOP-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-8629.
------------------------------------
Resolution: Won't Fix
> Add option for TableMapping to reload mapping file on match failure
> -------------------------------------------------------------------
>
> Key: HADOOP-8629
> URL: https://issues.apache.org/jira/browse/HADOOP-8629
> Project: Hadoop Common
> Issue Type: Improvement
> Components: util
> Reporter: Steve Loughran
> Priority: Minor
>
> As commented in HADOOP-7030, the table mapping topology mapper handles new node addition worse than the script mapping, because the table mapping is frozen for the life of the service.
> I propose adding an option (true by default?) for the class to look at the timestamp of the mapping file, and reload it on a change -if a hostname lookup failed.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org