You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/06/14 11:43:09 UTC
[GitHub] [flink] knaufk opened a new pull request #8741: [Flink 12752] Add
Option to Pass Seed for JobID Hash for StandaloneJobClusterEntrypoint
knaufk opened a new pull request #8741: [Flink 12752] Add Option to Pass Seed for JobID Hash for StandaloneJobClusterEntrypoint
URL: https://github.com/apache/flink/pull/8741
## What is the purpose of the change
In case of a standalone job cluster setup, we would like to generate random a {{JobID}} for every job, but the {{JobID}} nevertheless needs to stay constant between JobManager process restarts.
For this, I would like to add an additional command line options for the {{StandaloneJobClusterEntrypoint}} called {{jobId-seed}}. A manually specified jobId would still take precedence (not breaking current behavior):
## Brief change log
* Use "--job-id-seed" in K8s Resource Definition templates (4 minutes ago) <Konstantin Knauf>
* Adding job-id-seed parameter to StandaloneJobClusterEntrypoint (17 hours ago) <Konstantin Knauf>
* [hotfix] unify spelling of "JobID" in flink-container module (17 hours ago) <Konstantin Knauf>
## Verifying this change
* added tests in flink-container and flink-runtime module
* build a flink job cluster image locally
```
./build.sh --job-artifacts ../../flink-examples/flink-examples-streaming/target/flink-examples-streaming_2.11-1.9-SNAPSHOT-TopSpeedWindowing.jar --from-local-dist
FLINK_JOB_ARGUMENTS="--job-id-seed this-is-a-special-seed FLINK_JOB=org.apache.flink.streaming.examples.windowing.TopSpeedWindowing docker-compose up
```
and verify that the generate Job ID is stable
* follow instruction in flink-container/kubernetes/README.md to start a Job Cluster in Kubernetes with seed JobID
This change added tests and can be verified as follows:
## 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? yes
- If yes, how is the feature documented? flink-container/kubernetes/README.md
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services