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 "liang xie (JIRA)" <ji...@apache.org> on 2012/11/23 04:24:58 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13502997#comment-13502997 ] 

liang xie commented on HADOOP-8629:
-----------------------------------

I prefer to provide an admin cmd to reload by administrator
                
> 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 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