Steve Vaughan created HADOOP-18365:
--------------------------------------
Summary: Updated addresses are still accessed using the old IP
address
Key: HADOOP-18365
URL: https://issues.apache.org/jira/browse/HADOOP-18365
Project: Hadoop Common
Issue Type: Improvement
Components: common
Environment: Demonstrated in a Kubernetes environment running Java 11.
Reporter: Steve Vaughan
When the IPC Client recognizes that an IP address has changed, it updates the
server field and logs a message:
Address change detected. Old:
journalnode-1.journalnode.hdfs.svc.cluster.local/10.1.0.178:8485 New:
journalnode-1.journalnode.hdfs.svc.cluster.local/10.1.0.182:8485
Although the change is detected, the client will continue to connect to the old
IP address, resulting in repeated log messages. This is seen in managed
environments when JournalNode syncing is enabled and a JournalNode is
restarted, with the remaining nodes in the set repeatedly logging this message
when syncing to the restarted JournalNode.
The source of the problem is that the remoteId.address is not updated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
