Yes, for older releases operators may be marked as stuck due to delays
in setup, but for the provided stack trace, it is a wait between
heartbeats, not a wait for setup and activation.
Thank you,
Vlad
On 3/7/17 06:50, Sandesh Hegde wrote:
In older versions of Apex, heart beat loop waits for operator setup
and activate method to finish.
Check operator Setup and activate method.
On Tue, Mar 7, 2017 at 1:19 AM chiranjeevi vasupilli
<chiru....@gmail.com <mailto:chiru....@gmail.com>> wrote:
Hi Team,
In my application the reader operator window id got stuck and it
is not moved further. When we check the stack Trace we found the
below *TIMED_WAITING (on object monitor) *and container got
killed* after TIMEOUT_WINDOW_COUNT*.
Can you please tell me why the operator got stuck and unable to
proceed further.
"main" prio=10 tid=0x00007f1f8801d800 nid=0x11c1 in Object.wait()
[0x00007f1f8f0c6000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00007f112eb65360> (a java.lang.Object)
at
com.datatorrent.stram.engine*.StreamingContainer.heartbeatLoop(StreamingContainer.java:610)*
- locked <0x00007f112eb65360> (a java.lang.Object)
at
com.datatorrent.stram.engine.StreamingContainer.main(StreamingContainer.java:280)
Let me know if you need further information.
--
ur's
chiru
--
/Join us at ApexBigDataWorld-San Jose
<http://www.apexbigdata.com/san-jose.html>, April 4, 2017!/
http://www.apexbigdata.com/san-jose-register.html
