[
https://issues.apache.org/jira/browse/FLINK-12752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323256#comment-17323256
]
Flink Jira Bot commented on FLINK-12752:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Add Option to Pass Seed for JobID Hash for StandaloneJobClusterEntrypoint
> -------------------------------------------------------------------------
>
> Key: FLINK-12752
> URL: https://issues.apache.org/jira/browse/FLINK-12752
> Project: Flink
> Issue Type: Sub-task
> Components: flink-docker
> Reporter: Konstantin Knauf
> Assignee: Konstantin Knauf
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
