Re: Why assignTimestampsAndWatermarks parallelism same as map,it will not fired?
Posted by
Michael Latta on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/Why-assignTimestampsAndWatermarks-parallelism-same-as-map-it-will-not-fired-tp19733p19774.html
If you are using keyed messages in Kafka, or keyed streams in flink, then only partitions that get hashed to the proper value will get data. If not keyed messages, then yes they should all get data.
Michael
The event is running all the time in order,I don't know why one of the partitions does not receive data if not change parallelism?
发件人: Fabian Hueske <[hidden email]>
发送时间: 2018年4月25日 10:56
收件人: Timo Walther
抄送: user
主题: Re: Why assignTimestampsAndWatermarks parallelism same as map,it will not fired?
Hi,
This sounds like one of the partitions does not receive data. Watermark generation is data driven, i.e., the watermark can only advance if the TimestampAndWatermarkAssigner sees events.
By changing the parallelism between the map and the assigner, the events are shuffled across and hence there is no "empty" partition anymore.
I would check if one instance of your sources does not emit events.
Best, Fabian