[
https://issues.apache.org/jira/browse/FLINK-14537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961608#comment-16961608
]
Yun Tang edited comment on FLINK-14537 at 10/29/19 2:35 AM:
------------------------------------------------------------
[~ouyangwuli] Why not use grafana but influxdb cli to query metrics? What's
important, you actually did not talk about your solution to improve the
performance of Influxdb reporter.
Last but not least, from my experience, 13k measurements should not be
something InfluxDB cannot handle. I think 2 minutes for you to query seems too
long to be normal.
was (Author: yunta):
[~ouyangwuli] Why not use grafana but influxdb cli to query metrics? What's
important, you actually did not talk about your solution to improve the
performance of Influxdb reporter.
> 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)
