[
https://issues.apache.org/jira/browse/FLINK-12752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870878#comment-16870878
]
Konstantin Knauf commented on FLINK-12752:
------------------------------------------
[~1u0] Yes, originally I hoped there is some field in Kubernetes, which could
be used as the seed. After looking into it more, I now think, that no such
field exists. Nevertheless, I think, this is valuable because of the free-form
format and the provided templates. Additionally, this makes injecting the
{{JobID}} from outside more flexible for other environment, too.
> 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: Deployment / Docker
> Reporter: Konstantin Knauf
> Assignee: Konstantin Knauf
> Priority: Major
> Labels: pull-request-available
> 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}}. A manually
> specified jobId would still take precedence (not breaking current behavior):
> * --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
(v7.6.3#76005)
