Hi Chetan, I saw that the OperatorRequest was being created in the heartbeat loop and stopped tracing the code from there. I see now that it is queued up and executed when the end window is processed. My mistake, the issue I am seeing must be caused by an asynchronous task executing in the operator.
Thanks, Tim On Tue, Nov 10, 2015 at 10:38 AM, Chetan Narsude (cnarsude) < [email protected]> wrote: > It¹s called from operator thread. The heartbeat queues it up for the > operator thread to pick it up. > > Do you have example of having race conditions (in which case it would be a > bug not the design)? > > ‹ > Chetan > > > On 11/10/15, 10:31 AM, "Timothy Farkas" <[email protected]> wrote: > > >Why is committed called from the heart beat loop? Shouldn't it be called > >from the main operator thread? I think this is inconsistent with the > >contract provided for the rest of the callbacks. This is also causing race > >conditions in some operators. > >
