Details
-
Sub-task
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
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. job-id-seed and job-id are mutually exclusive.
- --jobId
- --jobId-seed
- (default)
On Kubernetes, this new command line argument would need to be set to a property which is stable over Pod Restarts but changes for different K8s Jobs or K8s Deployments.
Open Questions
- what available information to use a seed for deployments on Kubernetes?
Attachments
Issue Links
- blocks
-
FLINK-12885 Rename "Job Cluster" to "Application Cluster" in READMEs and Documentation
- Closed
- links to