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-9151] [Startup Shell Scripts] Export FLINK_CONF_DIR to job manager and task managers in standalone cluster mode (1.4.x) #5831

Closed
wants to merge 1 commit into
base: release-1.4
from

Conversation

Projects
None yet
1 participant
@facboy

facboy commented Apr 10, 2018

What is the purpose of the change

This pull request makes the standalone cluster scripts pass FLINK_CONF_DIR to the launched job managers and task managers, rather than relying on the default config dir on the target host.

Brief change log

  • Added export FLINK_CONF_DIR to config.sh and start_cluser.sh

Verifying this change

  • Manually verified the change by running a standalone cluster with a local FLINK_CONF_DIR environment variable set.

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: yes
  • 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

@facboy facboy changed the base branch from master to release-1.4 Apr 10, 2018

@facboy facboy changed the title from [FLINK-9151] [Startup Shell Scripts] Export FLINK_CONF_DIR to job manager and task managers in standalone cluster mode to [FLINK-9151] [Startup Shell Scripts] Export FLINK_CONF_DIR to job manager and task managers in standalone cluster mode (1.4.x) Apr 10, 2018

@facboy

This comment has been minimized.

Show comment
Hide comment
@facboy

facboy Apr 12, 2018

Actually this can be handled by env.ssh.opts provided your target servers allow you to send the FLINK_CONF_DIR env var in an ssh session.

facboy commented Apr 12, 2018

Actually this can be handled by env.ssh.opts provided your target servers allow you to send the FLINK_CONF_DIR env var in an ssh session.

@facboy facboy closed this Apr 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment