You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/07/28 14:48:00 UTC
[jira] [Commented] (FLINK-7246) Big latency shown on
operator.latency
[ https://issues.apache.org/jira/browse/FLINK-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105056#comment-16105056 ]
Stephan Ewen commented on FLINK-7246:
-------------------------------------
Have a look here, please to see the impact on latency parameters: https://ci.apache.org/projects/flink/flink-docs-master/dev/datastream_api.html#controlling-latency
We are currently changing this so that this parameter is not needed and you always get lower latency.
> Big latency shown on operator.latency
> -------------------------------------
>
> Key: FLINK-7246
> URL: https://issues.apache.org/jira/browse/FLINK-7246
> Project: Flink
> Issue Type: Bug
> Components: DataStream API, Metrics
> Affects Versions: 1.2.1
> Environment: Local
> Reporter: yinhua.dai
>
> I was running flink 1.2.1, and I have set metrics reporter to JMX to check latency of my job.
> But the result is that the latency I observerd is over 100ms even there is no processing in my job.
> And then I ran the example SocketWordCount streaming job, and again I saw the latency is over 100ms, I am wondering if there is something misconfiguration or problems.
> I was using start-local.bat and flink run to start up the job, all with default configs.
> Thank you in advance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)