Hi Jared,
I currently don't have a solid idea of what may be happening, but from the
stack dump you provided, it seems like the client connection you are using
in the Elasticsearch API call bridge is stuck, even after the cleanup.
Do you think there could be some issue with closing the client you
Here’s a more complete view of the task manager log from the start of this
occurrence:
2018-01-11 14:50:08.286 [heartbeat-filter -> input-trace-filter ->
filter-inactive-ds -> filter-duplicates
(ip-10-80-54-205.us-west-2.compute.internal:2181)] INFO
c.i.flink.shaded.zookeeper.org.apache.zooke
As another data point, here’s an except from a stack dump for the task manager:
"heartbeat-filter -> input-trace-filter -> filter-inactive-ds ->
filter-duplicates (5/10)-EventThread" #94 daemon prio=5 os_prio=0
tid=0x7f48c04d4800 nid=
0x68ef waiting on condition [0x7f48470eb000]
java.
I’m seeing sporadic issues where it appears that curator (or other) user
threads are left running after a stream shutdown, and then the user class
loader goes away and I get spammed with ClassNotFoundExceptions… I’m wondering
if this might have something to do with perhaps the UserClassLoader be
