ness configured
>>>>>>>> for
>>>>>>>> the session window ( the normal withLateNess() ) and this looks like a
>>>>>>>> session window was not collected and still is alive for some reason ( a
>>>>>>>> flink bug ? )
gt; https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/windows.html#getting-late-data-as-a-side-output
>>>>>>>>
>>>>>>>> On Thu, Apr 22, 2021 at 3:22 PM Vishal Santoshi <
>>>>>>>> vishal.santo...@gmail.com> wrote:
&g
vent-time-window-cannot-become-earlier-than-the-current.
>>>>>>>> and this seems to suggest a straight up filter, but I am not sure how
>>>>>>>> does
>>>>>>>> that filter works as in would it factor is the lateness when filtering
>>&
t;>>> [1]
>>>>>> https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/windows.html#getting-late-data-as-a-side-output
>>>>>>
>>>>>> On Thu, Apr 22, 2021 at 3:22 PM Vishal Santoshi <
>>>>>> vishal.
> vishal.santo...@gmail.com> wrote:
>>>>>
>>>>>> I saw
>>>>>> https://stackoverflow.com/questions/57334257/the-end-timestamp-of-an-event-time-window-cannot-become-earlier-than-the-current.
>>>>>> and this seems to suggest
ecome-earlier-than-the-current.
>>>>> and this seems to suggest a straight up filter, but I am not sure how does
>>>>> that filter works as in would it factor is the lateness when filtering ?
>>>>>
>>>>> On Thu, Apr 22, 2021 at 8:24
at filter works as in would it factor is the lateness when filtering ?
>>>>
>>>> On Thu, Apr 22, 2021 at 8:24 AM Vishal Santoshi <
>>>> vishal.santo...@gmail.com> wrote:
>>>>
>>>>> Well it was not a solution after all. We
s with this exception. The only thing I had done was to
>>>>> increase the lateness by 12 hours ( to a day ) in this pipe and restart
>>>>> from SP and it ran for 12 hours plus without issue. I cannot imagine that
>>>>> increasing the lateness crea
lateness to 2 days and that masked the issue which again
>> reared it's head after the 2 days ;lateness was over ( instead of the 1 day
>> ) before. This is very disconcerting.
>>
>> Caused by: java.lang.UnsupportedOperationException: The end timestamp of
>> an
ine that
>>>> increasing the lateness created this and the way I solved this was to
>>>> increase the lateness further. Could this be if there are TMs in the
>>>> cluster whose time is off ( as in not synchronized ) ?
>>>>
>>>>
gt; ) before. This is very disconcerting.
>>
>> Caused by: java.lang.UnsupportedOperationException: The end timestamp of
>> an event-time window cannot become earlier than the current watermark by
>> merging. Current watermark: 1619053742129 window: TimeWindow{start=
>> 16188
) before. This is very disconcerting.
Caused by: java.lang.UnsupportedOperationException: The end timestamp of an
event-time window cannot become earlier than the current watermark by
merging. Current watermark: 1619053742129 window: TimeWindow{start=
161883663, end=1618879580402}
On Wed, Apr 21
r the 2 days ;lateness was over ( instead of the 1 day
> ) before. This is very disconcerting.
>
> Caused by: java.lang.UnsupportedOperationException: The end timestamp of
> an event-time window cannot become earlier than the current watermark by
> merging. Current watermark: 16190
cannot become earlier than the current watermark by merging. Current
watermark: 1618966593999 window: TimeWindow{start=1618878336107, end=
1618880140466}
at org.apache.flink.streaming.runtime.operators.windowing.
WindowOperator$2.merge(WindowOperator.java:339
14 matches
Mail list logo
