[jira] [Updated] (HDFS-4870) periodically re-resolve hostnames in included and excluded datanodes list
[ https://issues.apache.org/jira/browse/HDFS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-4870: --- Labels: BB2015-05-TBR (was: ) > periodically re-resolve hostnames in included and excluded datanodes list > - > > Key: HDFS-4870 > URL: https://issues.apache.org/jira/browse/HDFS-4870 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Colin Patrick McCabe >Assignee: Colin Patrick McCabe >Priority: Minor > Labels: BB2015-05-TBR > Attachments: HDFS-4870.001.patch > > > We currently only resolve the hostnames in the included and excluded > datanodes list once-- when the list is read. The rationale for this is that > in big clusters, DNS resolution for thousands of nodes can take a long time > (when generating a datanode list in getDatanodeListForReport, for example). > However, if the DNS information changes for one of these hosts, we should > reflect that. A background thread could do these DNS resolutions every few > minutes without blocking any foreground operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-4870) periodically re-resolve hostnames in included and excluded datanodes list
[ https://issues.apache.org/jira/browse/HDFS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-4870: --- Assignee: Colin Patrick McCabe Affects Version/s: 2.0.5-alpha Status: Patch Available (was: Open) > periodically re-resolve hostnames in included and excluded datanodes list > - > > Key: HDFS-4870 > URL: https://issues.apache.org/jira/browse/HDFS-4870 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Colin Patrick McCabe >Assignee: Colin Patrick McCabe >Priority: Minor > Attachments: HDFS-4870.001.patch > > > We currently only resolve the hostnames in the included and excluded > datanodes list once-- when the list is read. The rationale for this is that > in big clusters, DNS resolution for thousands of nodes can take a long time > (when generating a datanode list in getDatanodeListForReport, for example). > However, if the DNS information changes for one of these hosts, we should > reflect that. A background thread could do these DNS resolutions every few > minutes without blocking any foreground operations. -- 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
[jira] [Updated] (HDFS-4870) periodically re-resolve hostnames in included and excluded datanodes list
[ https://issues.apache.org/jira/browse/HDFS-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-4870: --- Attachment: HDFS-4870.001.patch > periodically re-resolve hostnames in included and excluded datanodes list > - > > Key: HDFS-4870 > URL: https://issues.apache.org/jira/browse/HDFS-4870 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Colin Patrick McCabe >Priority: Minor > Attachments: HDFS-4870.001.patch > > > We currently only resolve the hostnames in the included and excluded > datanodes list once-- when the list is read. The rationale for this is that > in big clusters, DNS resolution for thousands of nodes can take a long time > (when generating a datanode list in getDatanodeListForReport, for example). > However, if the DNS information changes for one of these hosts, we should > reflect that. A background thread could do these DNS resolutions every few > minutes without blocking any foreground operations. -- 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
