LoggingResearch created YARN-11723:
--------------------------------------
Summary: Exposing Configuration Handling for Flow Name Shortening
in TimelineUtils
Key: YARN-11723
URL: https://issues.apache.org/jira/browse/YARN-11723
Project: Hadoop YARN
Issue Type: Improvement
Components: yarn
Affects Versions: 3.3.6
Environment: Version: 3.3.6
Location:
hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/timelineservice/TimelineUtils.java,
in the shortenFlowName method, lines 194-202.
Reporter: LoggingResearch
Attachments: TestShortenedFlowName.java, original-vs-log-enhanced.md
When configuring the maximum size for flow names using
yarn.timeline-service.flowname.max-size, users may inadvertently set this
parameter to a non-positive value, expecting the system to handle it correctly.
However, such misconfigurations lead to the flow name not being shortened, with
no indication given to the user about the issue. This can cause confusion as
the flow name remains unaltered, despite the expectation that it should be
shortened.
*Expected Behavior:*
The system should log a warning when an invalid configuration is detected,
informing the user that the flow name will not be shortened due to a
non-positive value being set for yarn.timeline-service.flowname.max-size.
*How-to-Fix:*
We propose adding log statements to expose the handling of invalid
configuration values when shortening flow names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
