[
https://issues.apache.org/jira/browse/STORM-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188545#comment-15188545
]
ASF GitHub Bot commented on STORM-1609:
---------------------------------------
Github user hustfxj commented on the pull request:
https://github.com/apache/storm/pull/1194#issuecomment-194629551
+1. I have a suggestion. we drop messages because Channel is not in good
state. I hope we should put the messages into buffer when Channel is not in
good state. Of course, we should drop the buffer if the channel is still not in
good state.
> Netty Client is not best effort delivery on failed Connection
> -------------------------------------------------------------
>
> Key: STORM-1609
> URL: https://issues.apache.org/jira/browse/STORM-1609
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Sanket Reddy
> Assignee: Sanket Reddy
>
> f Worker-A has connection to Worker-B that is unused ( and if Worker-B
> restarted), we drop messages because Channel is not in good state. Can we
> avoid message drop until we succeed in making new connection or a timeout?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
