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

jiapeng commented on STORM-1382:
--------------------------------

me too. the version of storm is 1.2.2

2019-02-15 22:36:59.028 o.a.s.m.n.Client client-boss-1 [ERROR] connection 
attempt 3 to Netty-Client-node02/192.168.1.102:6701 failed: 
java.net.ConnectException: 拒绝连接: node02/192.168.1.102:6701 2019-02-15 
22:36:59.028 o.a.s.u.StormBoundedExponentialBackoffRetry client-boss-1 [WARN] 
WILL SLEEP FOR 108ms (NOT MAX) 2019-02-15 22:36:59.029 o.a.s.d.executor main 
[INFO] Loaded executor tasks __system:[-1 -1] 2019-02-15 22:36:59.070 
o.a.s.d.executor main [INFO] Finished loading executor __system:[-1 -1]

> Netty Client connection failure error message is too alarming
> -------------------------------------------------------------
>
>                 Key: STORM-1382
>                 URL: https://issues.apache.org/jira/browse/STORM-1382
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>            Reporter: Paul Poulosky
>            Priority: Major
>
> The error message printed when a netty-client cannot connect to another 
> worker is worded in a way that our users are interpreting as a failure with 
> storm.
> There are times, such as at topology launch when such messages are normal as 
> not all of the workers have been launched on all of the supervisors yet.
> Other times, it is indicative of a failure (uncaught exception, OOM) on 
> another worker, but the end user believes that this client is failing, due to 
> the error message.
> eg:
> {noformat}
> 2015-12-03 12:28:53.338 b.s.m.n.Client [ERROR] connection attempt 10 to 
> Netty-Client-host1.grid.myco.com/10.1.2.3:6710 failed: 
> java.net.ConnectException: Connection refused: 
> host1.grid.myco.com/10.1.2.3:6710
> {noformat}
> We should change the message to be more informative to our end users as to 
> what happened, and it should not be an ERROR, but a Warning, as there are 
> occasions when one would expect to see this.



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

Reply via email to