答复: Why assignTimestampsAndWatermarks parallelism same as map，it will not fired？

Posted by 潘 功森 on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/Why-assignTimestampsAndWatermarks-parallelism-same-as-map-it-will-not-fired-tp19733p19773.html

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

2018-04-25 10:43 GMT+02:00 Timo Walther <[hidden email]>:

Hi,

did you set your time characteristics to even-time?

env.setStreamTimeCharacteristic(TimeCharacteristic.EventTime);

Regards,
Timo

Am 25.04.18 um 05:15 schrieb 潘 功森:

Hi all,


I use the same parallelism between map and assignTimestampsAndWatermarks , and it not fired, I saw the extractTimestamp and generateWatermark all is fine, but watermark is always not change and keep as min long value.

And then I changed parallelism and different with map, and windows fired.

I used Flink 1.3.2.

Is it a Flink bug?or others can give me why it not fired. It troubled me the whole day.


Best regards,

September