Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
For regular containers we have the yarn.application.classpath property, which allows users to add extra elements to the container's classpath.
However yarn services deliberately ignores this property to avoid incompatible class collision. However on systems where the configuration files for containers are located other than the path stored in $HADOOP_CONF_DIR, there is no way to modify the classpath to include other directories with the actual configuration.
Suggestion let's create a new property which allows us to add extra elements to the classpath generated for YARN service AM containers.
Attachments
Attachments
Issue Links
- causes
-
YARN-9575 Fix TestYarnConfigurationFields testcase failing
- Resolved