Skip to content
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.

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

[FLINK-15437][yarn] Apply dynamic properties early on client side. #10728

Closed
wants to merge 4 commits into from

Conversation

xintongsong
Copy link
Contributor

What is the purpose of the change

This PR applies dynamic properties early on client side, to make sure the client uses the correct configurations set via dynamic properties.

Brief change log

  • 475b642: Write yarn properties file without YarnClusterDescriptor.
  • 322a659: Apply dynamic properties early on client side.

Verifying this change

  • Updated FlinkYarnSessionCliTest#testDynamicProperties

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable)

@xintongsong
Copy link
Contributor Author

cc @wangyang0918 @tisonkun @kl0u

@flinkbot
Copy link
Collaborator

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit 322a659 (Tue Dec 31 05:18:13 UTC 2019)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!

Mention the bot in a comment to re-run the automated checks.

Review Progress

  • ❓ 1. The [description] looks good.
  • ❓ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ❓ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@flinkbot
Copy link
Collaborator

flinkbot commented Dec 31, 2019

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run travis re-run the last Travis build
  • @flinkbot run azure re-run the last Azure build

Copy link
Contributor

@wangyang0918 wangyang0918 left a comment

Choose a reason for hiding this comment

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

@xintongsong Thanks for your contribution. I think this PR is a good fix. We apply the dynamic properties earlier in the client and then ship the updated flink config to jobmanager. So we will not need to apply the dynamic properties again in the jobmanager. And i do not find out some negative effects.

For the magic yarn properties file, we keep the same behavior now and try to remove it in the next major release.

@@ -1045,10 +1031,6 @@ private ApplicationReport startAppMaster(
appMasterEnv.put(YarnConfigKeys.ENV_KRB5_PATH, remoteKrb5Path.toString());
}

if (dynamicPropertiesEncoded != null) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Since we have apply all the dynamic properties to the client uploaded flink configuration, so we will not need to set the ENV_DYNAMIC_PROPERTIES and parse it in the jobmanager. So YarnConfigKeys.ENV_DYNAMIC_PROPERTIES could be removed and all the usage on the jobmanager side should also be removed.

@@ -369,6 +372,14 @@ public Configuration applyCommandLineOptionsToConfiguration(CommandLine commandL
effectiveConfiguration.setInteger(TaskManagerOptions.NUM_TASK_SLOTS, Integer.parseInt(commandLine.getOptionValue(slots.getOpt())));
}

dynamicPropertiesEncoded = encodeDynamicProperties(commandLine);
if (dynamicPropertiesEncoded != null && !dynamicPropertiesEncoded.isEmpty()) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I think the null check is unnecessary since the encodeDynamicProperties will always return a NonNull value.

@xintongsong
Copy link
Contributor Author

@wangyang0918 Thanks for the review, comments addressed.

Copy link
Contributor

@wangyang0918 wangyang0918 left a comment

Choose a reason for hiding this comment

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

@xintongsong Thanks for addressing my comment. LGTM now.

Copy link
Member

@tisonkun tisonkun left a comment

Choose a reason for hiding this comment

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

LGTM. Merging...

@tisonkun tisonkun closed this in 367765b Jan 3, 2020
@xintongsong
Copy link
Contributor Author

Thanks for the review, @tisonkun.

tisonkun pushed a commit that referenced this pull request Jan 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants