Hi KristoffSC, I'd strongly suggest not blocking the task thread if it involves external services. RPC notification cannot be processed and checkpoints are delayed when the task thread is blocked. That's what AsyncIO is for.
If your third party library just takes a few ms to finish computation without any external service, that would be totally fine though and would be the normal case of compute-intensive tasks where few events come in and still saturate a cluster quickly (e.g., text mining, data cleansing, or even evaluation of a complex model). On Tue, Nov 24, 2020 at 10:39 PM KristoffSC <krzysiek.chmielew...@gmail.com> wrote: > Hi Arvid, > Thank you for your answer. > > And what if a) would block task's thread? > Let's say I'm ok with making entire task thread to wait on this third party > lib. > > In that case I would be safe from having this exception even though I would > not use AsyncIO? > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ > -- Arvid Heise | Senior Java Developer <https://www.ververica.com/> Follow us @VervericaData -- Join Flink Forward <https://flink-forward.org/> - The Apache Flink Conference Stream Processing | Event Driven | Real Time -- Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany -- Ververica GmbH Registered at Amtsgericht Charlottenburg: HRB 158244 B Managing Directors: Timothy Alexander Steinert, Yip Park Tung Jason, Ji (Toni) Cheng
