LoggingResearch created MAPREDUCE-7490:
------------------------------------------
Summary: Exposing Default Handling of Misconfigurations to Users
in ManifestCommitterConfig
Key: MAPREDUCE-7490
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7490
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: mapreduce-client
Affects Versions: 3.3.6
Environment: Version: {{`3.3.6`}}
Location:
{{{}`hadoop/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/lib/output/committer/manifest/ManifestCommitterConfig.java`{}}}，
in {{`createSubmitter`}} method, from Line 385 - 388.
Reporter: LoggingResearch
Attachments: ManifestCommitterConfigTest.java,
original-vs-log-enhanced.md
When users accidentally set the parameter
{{mapreduce.manifest.committer.io.threads}} to a negative value (e.g., -80 due
to a typographical error), the system automatically resets the value to the
default of 32. While this handling prevents errors, it may lead to performance
degradation. However, without any system output indicating that the default
value has been applied, users might mistakenly believe that the system is
performing optimally with their intended setting of 80.
*Expected Behavior:*
If the parameter {{mapreduce.manifest.committer.io.threads}} is set incorrectly
due to a typographical error, the system should output a warning to notify
users of the misconfiguration and the use of the default value.
*How-to-Fix:*
We propose improving system observability by adding logging.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
