Hi XiangWei, this could be a resource leak, i.e. a socket not getting closed, but I was unable to reproduce that behaviour. Maybe Chesnay (cc'd) has an idea on how/ where this may happen.
Can you tell us a bit more on what you where doing / how the webinterface was used? Is there a way to reproduce the behaviour? Nico PS: please don't post text output as images - this makes reading/finding the email and following the thread much more complicated. Please copy the text instead. On Thursday, 29 June 2017 06:36:47 CEST XiangWei Huang wrote: > There were a lot of connections which state is “CLOSE_WAIT” appeared when > a few days later after flink jobManager is started. > > The process name of pid 20180 is 'flink jobManager'. > The stack trace is blow:
signature.asc
Description: This is a digitally signed message part.
