gt;>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/a-lot-of-connections-in-state-CLOSE-WAIT-tp14046
336050.n4.nabble.com/a-lot-of-connections-in-state-CLOSE-WAIT-tp14046p14463.html
To unsubscribe from a lot of connections in state "CLOSE_WAIT",click
here.
NAML
<http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=
a-lot-of-connections-in-state-CLOSE-WAIT-tp14046p14422.html>
>>>> Sent from the Apache Flink User Mailing List archive. mailing list archive
>>>> at Nabble.com.
>>>>
>
>
>
> If you reply to this email, your messa
So this /only/ happens when you select a metric? Without a selected
metric everything works fine?
Are the metrics you selected shown correctly?
Did you modify the "jobmanager.web.refresh-interval" setting? (maybe
check the flink-conf-yaml for the current setting)
On 26.07.2017 04:57, XiangWe
hi,
The browser i am using is Google Chrome with version 59.0.3071.115 and the
issue persists when i tried Firefox.
Regards,
XiangWei
> 在 2017年7月25日，17:48，Chesnay Schepler 写道：
>
> Hello,
>
> Could you tell us which browser you are using, including the version?
> (and maybe try out if the iss
Hello,
Could you tell us which browser you are using, including the version?
(and maybe try out if the issue persists with a different one)
Regards,
Chesnay
On 25.07.2017 05:20, XiangWei Huang wrote:
hi,
Sorry for replying so late.
I have met this issue again and the list is constantly keep g
hi,
Sorry for replying so late.
I have met this issue again and the list is constantly keep growing even if
i close the page ,until the website is been unavailable.
This issue appeared each time i add metrics for a job from web ui.
by the way ,the version of Flink is 1.3.1
Regards,
Xia
Hello,
is this list constantly growing? If you reload the WebUI do they pile up
again?
My guess would be the watermarks display is overloading the metrics handler.
If i remember correctly the WebUI keeps fetching the watermark metrics
regardless
of what page you're looking at.
Things to inv
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 reprod
