[
https://issues.apache.org/jira/browse/HDFS-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-10438:
---------------------------------
Attachment: HDFS-10438.001.patch
I'm attaching a patch that uses the lifeline address in the string that gets
logged if a lifeline address is configured. I also updated a test to check for
the correct string representation. While working on this, I noticed that
{{MiniDFSCluster}} was not quite doing the right thing for copying the lifeline
address configuration key in a multi-nameservice/multi-namenode setup.
> When NameNode HA is configured to use the lifeline RPC server, it should log
> the address of that server.
> --------------------------------------------------------------------------------------------------------
>
> Key: HDFS-10438
> URL: https://issues.apache.org/jira/browse/HDFS-10438
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, namenode
> Reporter: KWON BYUNGCHANG
> Assignee: Chris Nauroth
> Priority: Minor
> Attachments: HDFS-10438.001.patch
>
>
> As reported by [~magnum]:
> I have configured below
> {code}
> dfs.namenode.servicerpc-address.xdev.nn1=my.host.com:8040
> dfs.namenode.lifeline.rpc-address.xdev.nn1=my.host.com:8041
> {code}
> servicerpc port is 8040, lifeline port is 8041.
> however zkfc daemon is logging using servicerpc port.
> It may cause confusion.
> thank you.
> {code}
> 2016-05-19 19:18:40,566 WARN ha.HealthMonitor
> (HealthMonitor.java:doHealthChecks(207)) - Service health check failed for
> NameNode at my.host.com/10.114.87.91:8040: The NameNode has no resources
> available
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
