[
https://issues.apache.org/jira/browse/FLINK-29801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635341#comment-17635341
]
yuemeng commented on FLINK-29801:
---------------------------------
[~ruanhang1993] [~zhuzh]
Firstly, thanks a lot for your reply
The following answer to your 2 question
# Each implementation of OperatorCoordinator will hold the metric group
instance that can be registered for anything they wanted. this feature is not
only for SourceCoordinator, eg: what about the other operator coordinators who
don't have a context
# Each operator coordinator's metric group is distinguished by metric group
name
Secondly
This implement already worked in our product env, if we had or wanted a new
design, we can push it forward and finish quickly because we real need it
> OperatorCoordinator need open the way to operate metricGroup interface
> ----------------------------------------------------------------------
>
> Key: FLINK-29801
> URL: https://issues.apache.org/jira/browse/FLINK-29801
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: yuemeng
> Assignee: yuemeng
> Priority: Major
> Labels: pull-request-available
>
> Currently, We have no way to get metric group instances in OperatorCoordinator
> In some cases, we may report some metric in OperatorCoordinator such as Flink
> hudi integrate scene， some meta will send to operator coordinator to commit
> to hdfs or hms
> but we also need to report some metrics in operator coordinator for monitor
> purpose
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
