You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/06/04 11:46:00 UTC
[jira] [Updated] (FLINK-12594) Make Job ID Configurable for a Job
Cluster
[ https://issues.apache.org/jira/browse/FLINK-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger updated FLINK-12594:
-----------------------------------
Component/s: Runtime / Coordination
> Make Job ID Configurable for a Job Cluster
> ------------------------------------------
>
> Key: FLINK-12594
> URL: https://issues.apache.org/jira/browse/FLINK-12594
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.8.0
> Reporter: Chaoran Yu
> Priority: Major
>
> Currently the job ID is only configurable for a job in a session cluster. If a job is launched as a job cluster, the job ID is always the default value of 00000000000000000000000000000000 without an option to manually set it. This [thread|[http://mail-archives.apache.org/mod_mbox/flink-user/201811.mbox/%3CCAKiyyaE+wx72gAwgDbLuThZKJR8VDPUid0Q1S=qx91pDf3=zKw@mail.gmail.com%3E]] in the mailing list also talked about the same issue. It should be made configurable in the job cluster case.
> In the [documentation|[https://github.com/apache/flink/tree/master/flink-container/kubernetes]] for running a job cluster on Kubernetes, it's mentioned that the job ID is configurable via the `--job-id` flag, which is false because it's not implemented anywhere. The documentation should be fixed until this feature is implemented.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)