You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (JIRA)" <ji...@apache.org> on 2019/06/05 21:25:00 UTC
[jira] [Updated] (FLINK-12752) Add Option to Pass Seed for JobID
Hash for StandaloneJobClusterEntrypoint
[ https://issues.apache.org/jira/browse/FLINK-12752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Knauf updated FLINK-12752:
-------------------------------------
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}}. 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?
was:
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.
> 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
> Reporter: Konstantin Knauf
> Assignee: Konstantin Knauf
> Priority: Major
>
> 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)