[
https://issues.apache.org/jira/browse/FLINK-14537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961243#comment-16961243
]
Yun Tang commented on FLINK-14537:
----------------------------------
I think the main cause is due to many unnecessary tags, which is still in
discussion of https://issues.apache.org/jira/browse/FLINK-13418 .
If your environment suffers from too many kafka metrics, you could also pass
[{{flink.disable-metrics}}|https://github.com/apache/flink/blob/96640cad3d770756cb6e70c73b25bd4269065775/flink-connectors/flink-connector-kafka-base/src/main/java/org/apache/flink/streaming/connectors/kafka/FlinkKafkaConsumerBase.java#L106]
into consumer properties to disable kafka reporting metrics via Flink.
> Improve influxdb reporter performance for kafka source/sink
> -----------------------------------------------------------
>
> Key: FLINK-14537
> URL: https://issues.apache.org/jira/browse/FLINK-14537
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.9.1
> Reporter: ouyangwulin
> Priority: Minor
> Fix For: 1.10.0, 1.9.2, 1.11.0
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> In our product env, our datasource mostly from kafka source. and influxdb
> report use kafka topic and partition for create infuxdb measurements, It
> makes 13531 measurements in influxdb. so It trouble for get measurements
> which we want get the metric data, and It exaust performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
