[
https://issues.apache.org/jira/browse/FLINK-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855402#comment-16855402
]
Zhu Zhu edited comment on FLINK-12684 at 6/4/19 7:03 AM:
---------------------------------------------------------
Hi [~richard.moorhead], metric reporters are flink cluster level components,
thus their configurations are fixed after the flink cluster is started, and
cannot be changed when submitting jobs to the cluster.
If you are using Flink in yarn mode rather the standalone mode, and just want
to have different metric reporter configurations for different yarn
applications(to serve different jobs), you can override flink configurations
via *-D/-yD* options when starting yarn session(in session mode) or submitting
job(in per job mode).
was (Author: zhuzh):
Hi [~richard.moorhead], metric reporters are session level components, thus
their configurations are fixed after the session is started, and cannot be
changed when submitting jobs to the session.
If you are using Flink in yarn mode rather the standalone mode, and just want
to have different metric reporter configurations for different yarn
sessions(they can serve different jobs), you can override flink configurations
via *-D/-yD* options when starting yarn session(in session mode) or submitting
job(in per job mode).
> User defined configuration for per job clusters
> -----------------------------------------------
>
> Key: FLINK-12684
> URL: https://issues.apache.org/jira/browse/FLINK-12684
> Project: Flink
> Issue Type: New Feature
> Components: Command Line Client, Runtime / Configuration
> Reporter: Richard Moorhead
> Priority: Major
>
> We have a use case where we need to be able to provide job specific
> configuration to a metrics reporter. In other words metrics reporting needs
> to be done at a per job basis rather than static configuration derived from
> the flink installation. In general would having the ability to provide user
> defined config (overrides) at job submission time be a reasonable feature?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
