Skip to content

TEZ-4685: DagAppMaster is not picking tez-site.xml from classpath in zookeeper mode #458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Aggarwal-Raghav wants to merge 1 commit into from
Closed

TEZ-4685: DagAppMaster is not picking tez-site.xml from classpath in zookeeper mode #458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion tez-dag/src/main/java/org/apache/tez/dag/app/DAGAppMaster.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@
package org.apache.tez.dag.app;


import static org.apache.tez.frameworkplugins.FrameworkMode.STANDALONE_ZOOKEEPER;

import java.io.File;
import java.io.FileInputStream;
Expand Down Expand Up @@ -2429,7 +2430,10 @@ public static void main(String[] args) {
Objects.requireNonNull(appSubmitTimeStr,
ApplicationConstants.APP_SUBMIT_TIME_ENV + " is null");

Configuration conf = new Configuration();
Configuration conf =
STANDALONE_ZOOKEEPER.name().equals(System.getenv(TezConstants.TEZ_FRAMEWORK_MODE))
? new TezConfiguration()
: new Configuration();
Comment on lines -2432 to +2436

@abstractdog abstractdog Feb 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be kept somehow in FrameworkUtils, like FrameworkUtils.getInitialConfiguration()
because we might want to hide the details of this "hack" from DAGAppMaster.

Why I call it a hack: it's not because the solution is bad, it's because of the current design, which leads to a catch-22:

  1. we need a Configuration
  2. for that we need to know the framework mode
  3. to know the framework mode and get framework client/server classes we need a Configuration object: getFrameworkService(conf)

so we cannot do anything better than to achieve original Configuration by the value stored in environment...which is fine, but DAGAppMaster's already overwhelmed logic should not contain such a thing

@ayushtkn ayushtkn Feb 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@abstractdog do you have pointer what is different in STANDALONE_ZOOKEEPER that it doesn't work here but does work in YARN mode?

@abstractdog abstractdog Feb 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, that's a good question: I guess here is where we might want to get back to the original motivation: whether a standalone TezAM docker container needs a tez-site.xml on its classpath (and if so, could it read) or if there is another way to configure it... isn't TEZ-4014 or some earlier work already taking care of this? what do you think @Aggarwal-Raghav ?

tez/tez-common/src/main/java/org/apache/tez/common/TezUtilsInternal.java

Lines 100 to 105 in f09ba7f

for (String confFile : confFromXml.getTrimmedStringCollection(TezConfiguration.TEZ_AM_STANDALONE_CONFS)) {
try (InputStream additionalInput = ClassLoader.getSystemResourceAsStream(confFile)) {
Configuration additionalConfFromXml = TezUtilsInternal.readTezConfigurationXml(additionalInput);
confFromXml.addResource(additionalConfFromXml);
}
}

@Aggarwal-Raghav Aggarwal-Raghav Feb 20, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll get back on this TEZ-4014 analysis in couple of days.

@Aggarwal-Raghav Aggarwal-Raghav Feb 21, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @abstractdog, for pointing out TEZ-4014.It works well, provided we pass TEZ_FRAMEWORK_MODE=STANDALONE_ZOOKEEPER as an environment variable (using the --env-file or -e flag in the docker run command) and ensure tez-site.xml is in the classpath.

Without this environment variable, it defaults back to YARN mode. I might have missed passing the -e flag initially while working on TEZ-4682 stared using with new TezConfiguration() as in current TEZ-4682 PR 551075b and never checked back :-(

@Aggarwal-Raghav Aggarwal-Raghav Feb 21, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll close this JIRA then


AMExtensions amExtensions = getFrameworkService(conf).getAMExtensions();
DAGProtos.ConfigurationProto confProto = amExtensions.loadConfigurationProto();
Expand Down