LoggingResearch created HADOOP-19268:
----------------------------------------
Summary: Improve Logging for Empty or Missing Socket Factory
Configuration
Key: HADOOP-19268
URL: https://issues.apache.org/jira/browse/HADOOP-19268
Project: Hadoop Common
Issue Type: Improvement
Components: common
Affects Versions: 3.3.6
Environment: Hadoop Version: {{`3.3.6`}}
Location:
{{{}`hadoop/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetUtils.java`{}}},in
{{`getDefaultSocketFactory`}} method. Lines 126 - 129.
Reporter: LoggingResearch
Attachments: TestNetUtils.java, original-vs-log-enhanced.md
In the current implementation of the {{NetUtils.getDefaultSocketFactory}}
method, when the configuration parameter
{{hadoop.rpc.socket.factory.class.default}} is not set or is empty, the method
silently defaults to using the standard {{{}SocketFactory{}}}. However, this
lack of logging can make it difficult to diagnose configuration issues. We
propose enhancing the code with logging to warn users when this situation
occurs.
*Expected Behavior:*
When the {{hadoop.rpc.socket.factory.class.default}} configuration parameter is
missing or empty, a warning log should be generated, informing the user that
the system is defaulting to the standard {{{}SocketFactory{}}}.
*How-to-Fix:*
We propose to expose this relationship by logging a warning when the
{{hadoop.rpc.socket.factory.class.default}} parameter is missing or empty.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
