LoggingResearch created HADOOP-19266:
----------------------------------------
Summary: Improve Logging for User Account Update Time
Configuration in ShellBasedIdMapping Constructor
Key: HADOOP-19266
URL: https://issues.apache.org/jira/browse/HADOOP-19266
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/security/ShellBasedIdMapping.java`{}}},
in {{{}`{}}}{*}{{init}}{*}{{{}`{}}}method. Lines 114-120.
Reporter: LoggingResearch
Attachments: TestShellBasedIdMapping.java, original-vs-log-enhanced.md
The original implementation of the {{ShellBasedIdMapping}} constructor lacks
detailed logging about the configuration of the user account update time
({{{}usergroupid.update.millis{}}}). When this time is set to a value less than
1 minute, the system automatically adjusts it to the minimum of 1 minute
without providing clear feedback to the user. This can lead to confusion and
difficulty in troubleshooting if the user is unaware that their configuration
was overridden. By adding detailed logs, we can ensure that users are informed
about the exact configuration being applied, making it easier to diagnose
potential issues related to configuration.
*Expected Behavior:*
When the {{ShellBasedIdMapping}} constructor is invoked, the system should log
the user-configured update time for user accounts. If the update time is below
the minimum threshold (1 minute), the system should log a warning indicating
that the minimum value of 1 minute will be used instead.
*How-to-Fix:*
We propose to expose such a relationship by adding detailed logging statements
to inform the user about the configuration status.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]