LoggingResearch created HDFS-17614:
--------------------------------------
Summary: Logging Configuration Changes in
BlackListBasedTrustedChannelResolver
Key: HDFS-17614
URL: https://issues.apache.org/jira/browse/HDFS-17614
Project: Hadoop HDFS
Issue Type: Improvement
Components: hdfs
Affects Versions: 3.3.6
Environment: Version: {{`3.3.6`}}
Location:
{{{}`hadoop/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/datatransfer/BlackListBasedTrustedChannelResolver.java`{}}}.
In {{`setConf`}} method, lines 100-108, 117-125
Reporter: LoggingResearch
Attachments: TestBlackListBasedTrustedChannelResolver.java,
original-vs-log-enhanced.md
The {{BlackListBasedTrustedChannelResolver}} class is responsible for setting
server and client blacklists based on configuration settings. However, the
current implementation lacks sufficient logging, making it difficult to trace
which configuration is applied during runtime. This enhancement proposes to add
logging to the {{setConf}} method to better expose the relationship between
configuration settings and their applied behavior.
*Expected Behavior:*
The system should log specific information about whether the server or client
variable blacklist is enabled and which file and expiry time are being used.
This will aid in debugging and monitoring the configuration settings applied
during the system's operation.
*How-to-Fix:*
We propose to expose the relationship between the configuration settings and
the applied behavior by adding logs in the {{setConf}} method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
