Yes, you are right. In other tasks the lock is not strictly necessary but we
have one method in the base class that covers all tasks.
> On 11 Mar 2016, at 05:04, Ma GuoWei wrote:
>
> it is very helpful。 thanks a lot
>
> now i know the souce task needs the lock。
>
> Other tasks like the Stream
it is very helpful。 thanks a lot
now i know the souce task needs the lock。
Other tasks like the StreamTask will handle broadcast and checkpoint then
process element
so lock is “no use” in those tasks。
am i right？
thanks your help very much！
发自我的 iPhone
> 在 2016年3月10日，下午7:45，Aljoscha Krett
Hi,
that call needs to be in the lock scope because we need to ensure that no
element processing/element emission happens while we forward the checkpoint
barrier and perform the checkpoint.
Let me illustrate with an example. Say we have a source. What can happen in the
source if the call is not
hi,all
Why does the broadcastCheckpointBarrier need in the lock scope?
thanks a lot.
[cid:3612d450-1757-4dcb-9bb5-0d0cd8b89b1a]
