[ 
https://issues.apache.org/jira/browse/STORM-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470428#comment-16470428
 ] 

zhangbiao commented on STORM-3055:
----------------------------------

this problem can be reproduced by:
first set up 2 two supervisor (name a, b), each with one slot, and submit a 
topology with network traffic between two works.
then the kill one supervisor (name a), remove the local state with the 
supervisor.  and kill work supervisored by a. then restart supervisor a
by follow this you can see worker on b print error log.
(remove the local state is to simulate localState corruption, which happens on 
our production environment)

> never refresh connection
> ------------------------
>
>                 Key: STORM-3055
>                 URL: https://issues.apache.org/jira/browse/STORM-3055
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-client, storm-core
>    Affects Versions: 2.0.0, 1.1.1
>            Reporter: zhangbiao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> in our enviroment some worker's connection to other worker being closed and 
> never reconnect,
> the log show's that 
> 2018-05-02 10:28:49.302 o.a.s.m.n.Client 
> Thread-90-disruptor-worker-transfer-queue [ERROR] discarding 1 messages 
> because the Netty client to Netty-Client-/192.168.31.1:6800 is being closed
> ......
> 2018-05-02 11:00:29.540 o.a.s.m.n.Client 
> Thread-90-disruptor-worker-transfer-queue [ERROR] discarding 1 messages 
> because the Netty client to Netty-Client-/192.168.31.1:6800 is being closed
> the log shows that it never can reconnect again. i can only fix it after 
> restart the topo, 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to