Prateek Agarwal created HDFS-17005:
--------------------------------------
Summary: NameJournalStatus JMX is not updated with new JN IP
address on JN host change
Key: HDFS-17005
URL: https://issues.apache.org/jira/browse/HDFS-17005
Project: Hadoop HDFS
Issue Type: Bug
Components: journal-node
Affects Versions: 3.3.4, 2.10.2, 2.8.2
Reporter: Prateek Agarwal
Whenever a JournalNode host gets replaced, 'org.apache.hadoop.ipc.Client' is
able to refresh the new JournalNode IP by re-resolving the JN DNS or host.
However, the JMX metrics exposed by Namenode still point to the stale JN IP
address. For example:
{code}
"NameJournalStatus" : "[{\"manager\":\"QJM to [10.92.29.151:8485,
10.94.17.167:8485, 10.92.59.158:8485]\",\"stream\":\"Writing segment beginning
at txid 93886612. \\n10.92.29.151:8485 (Written txid 93894676),
10.94.17.167:8485 (Written txid 93894674 (2 txns/1ms behind)),
10.92.59.158:8485 (Written txid
93894676)\",\"disabled\":\"false\",\"required\":\"true\"},{\"manager\":\"FileJournalManager(root=/data/1/dfs/name-data)\",\"stream\":\"EditLogFileOutputStream(/data/1/dfs/name-data/current/edits_inprogress_0000000000093886612)\",\"disabled\":\"false\",\"required\":\"false\"}]",
{code}
The IP address '10.92.29.151' isn't updated even if the JN node now points to
an updated IP address, say, '10.36.72.221'.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
