Hi Anil,
if I researched correctly we are talking about these changes [1]. I
don't know if you can back port it, but I hope this helps.
Regards,
Timo
[1] https://issues.apache.org/jira/browse/FLINK-9304
Am 07.11.18 um 17:41 schrieb Anil:
Hi Till,
Thanks for the reply. Is there any
Hi Till,
Thanks for the reply. Is there any particular patch I can use as
upgrading to Flink 1.6 is not an option for me at the moment.
Regards,
Anil.
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Hi Anil,
as Stephan stated, the fix is not included in Flink 1.4.2 but in the later
version of Flink. Can you upgrade to Flink 1.5.5 or Flink 1.6.2 to check
whether the problem still occurs?
Cheers,
Till
On Sun, Oct 28, 2018 at 8:55 AM Anil wrote:
> I do see the same error but in case differen
I do see the same error but in case different situation. I'm not cancelling
the job. Below is my error stack trace. SwiglobeZoneFromLatLong is my UDF
name. Is this error something ignorable. I'm using flink 1.4.2.
Thanks in advance.
```
{"debug_level":"ERROR","debug_timestamp":"2018-10-28
06:40
Agreed.
It is fixed in 1.5 and in the 1.4.x branch. The fix came after 1.4.2, so it
s not released as of now.
On Tue, Apr 17, 2018 at 7:47 PM, Ken Krugler
wrote:
> Hi Timo,
>
> [Resending from an address the Apache list server likes…]
>
> I discussed this with Till during Flink Forward, and he
Hi Timo,
[Resending from an address the Apache list server likes…]
I discussed this with Till during Flink Forward, and he said it looks like the
expected result when cancelling, as that will cause all operators to be
interrupted, which in turn generates the stack trace I’m seeing.
As to wheth
Hi Ken,
as you can see here [1], Flink interrupts the timer service after a
certain timeout. If you want to get rid of the exception, you should
increase "task.cancellation.timers.timeout" in the configuration.
Actually, the default is already set to 7 seconds. So your exception
should not b
