[jira] [Updated] (HDFS-5055) nn->2nn ignores dfs.namenode.secondary.http-address
[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-5055: -- Attachment: HDFS-5055.1.patch Thanks Jing. Here is the updated patch. > nn->2nn ignores dfs.namenode.secondary.http-address > --- > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 2.1.0-beta >Reporter: Allen Wittenauer >Assignee: Vinay >Priority: Blocker > Labels: regression > Attachments: HDFS-5055.1.patch, HDFS-5055.patch, HDFS-5055.patch > > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- 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-5055) nn->2nn ignores dfs.namenode.secondary.http-address
[
https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-5055:
--
Attachment: HDFS-5055.patch
[~vinayrpet] Thanks for jumping on this. The patch looks good. I updated the
patch with a small change.
Instead of:
{code}
String machine = imageListenAddress.getHostName();
if (machine == null || machine.isEmpty() || machine.equals("0.0.0.0")) {
machine = null;
}
{code}
the update patch has:
{code}
String machine = imageListenAddress.getAddress().isAnyLocalAddress() ?
null : imageListenAddress.getHostName();
{code}
> nn->2nn ignores dfs.namenode.secondary.http-address
> ---
>
> Key: HDFS-5055
> URL: https://issues.apache.org/jira/browse/HDFS-5055
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.1.0-beta
>Reporter: Allen Wittenauer
>Assignee: Vinay
>Priority: Blocker
> Labels: regression
> Attachments: HDFS-5055.patch, HDFS-5055.patch
>
>
> The primary namenode attempts to connect back to (incoming hostname):port
> regardless of how dfs.namenode.secondary.http-address is configured.
--
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-5055) nn->2nn ignores dfs.namenode.secondary.http-address
[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated HDFS-5055: - Assignee: Vinay Target Version/s: 2.1.0-beta Status: Patch Available (was: Open) > nn->2nn ignores dfs.namenode.secondary.http-address > --- > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 2.1.0-beta >Reporter: Allen Wittenauer >Assignee: Vinay >Priority: Blocker > Labels: regression > Attachments: HDFS-5055.patch > > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- 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-5055) nn->2nn ignores dfs.namenode.secondary.http-address
[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5055: Attachment: HDFS-5055.patch Attaching a simple patch to use the behavior of HDFS-3404 only in case of wildcard addresses. I hope this solves the issue > nn->2nn ignores dfs.namenode.secondary.http-address > --- > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 2.1.0-beta >Reporter: Allen Wittenauer >Priority: Blocker > Labels: regression > Attachments: HDFS-5055.patch > > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- 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-5055) nn->2nn ignores dfs.namenode.secondary.http-address
[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-5055: --- Labels: regression (was: ) > nn->2nn ignores dfs.namenode.secondary.http-address > --- > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 2.1.0-beta >Reporter: Allen Wittenauer >Priority: Blocker > Labels: regression > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- 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-5055) nn->2nn ignores dfs.namenode.secondary.http-address
[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-5055: --- Summary: nn->2nn ignores dfs.namenode.secondary.http-address (was: nn<->2nn ignores dfs.namenode.secondary.http-address) > nn->2nn ignores dfs.namenode.secondary.http-address > --- > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 2.1.0-beta >Reporter: Allen Wittenauer >Priority: Blocker > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- 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-5055) nn<->2nn ignores dfs.namenode.secondary.http-address
[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-5055: --- Summary: nn<->2nn ignores dfs.namenode.secondary.http-address (was: nn<->2nn ignore dfs.namenode.secondary.http-address) > nn<->2nn ignores dfs.namenode.secondary.http-address > > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 2.1.0-beta >Reporter: Allen Wittenauer >Priority: Blocker > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- 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
