LoggingResearch created HADOOP-19263:
----------------------------------------
Summary: Enhance Logging for Timeout Configuration in
Client.getTimeout
Key: HADOOP-19263
URL: https://issues.apache.org/jira/browse/HADOOP-19263
Project: Hadoop Common
Issue Type: Improvement
Components: common
Affects Versions: 3.3.6
Environment: Hadoop Version: {{3.3.6}}
Location:
{{{}`Breadcrumbshadoop/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Client.java`{}}},
in {{`getTimeout`}} method. Lines 208-212.
Reporter: LoggingResearch
Attachments: ClientTest.java, original-vs-log-enhanced.md
The original implementation of the {{Client.getTimeout}} method does not
provide detailed logging when it falls back to default behaviors based on the
configuration. Specifically, when the {{ipc.client.rpc.timeout}} parameter is
set to an invalid value (less than or equal to zero), the method either uses
the ping interval as the timeout or returns a default value of {{-1}} depending
on whether {{ipc.client.ping}} is enabled. This lack of logging can make it
difficult for users to understand why certain timeout values are being used,
leading to potential confusion and difficulty in troubleshooting. By adding
logging statements, the system can inform users about the decisions being made
based on their configurations.
*Expected Behavior:*
When the {{Client.getTimeout}} method is invoked, the system should log
detailed information about the timeout configuration, including whether the
{{ipc.client.ping}} is enabled or disabled, and how this affects the timeout
value being used.
*How-to-Fix:*
We propose to enhance the method by adding logging statements that inform the
user about the configuration decisions being made. This will improve
transparency and make the system easier to debug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
