You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Ethan Li (JIRA)" <ji...@apache.org> on 2019/08/10 22:25:00 UTC
[jira] [Updated] (STORM-3376) Storm drops messages in the interval
between server bind and callback registration
[ https://issues.apache.org/jira/browse/STORM-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Li updated STORM-3376:
----------------------------
Fix Version/s: (was: 2.0.1)
2.1.0
> Storm drops messages in the interval between server bind and callback registration
> ----------------------------------------------------------------------------------
>
> Key: STORM-3376
> URL: https://issues.apache.org/jira/browse/STORM-3376
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-client
> Affects Versions: 2.0.0
> Reporter: Stig Rohde Døssing
> Assignee: Stig Rohde Døssing
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> This is one of the causes of unstable integration tests.
> When a worker starts, WorkerState boots up a Server, which binds Netty to a port in order to receive messages from other workers. Slightly later, we register a callback with the server that defines where the Server should deliver received messages.
> In the interim between binding the port and registering the callbacks, Storm quietly discards any received messages.
> Other workers will happily send messages to the worker that is not ready, as the sending side considers an open connection to be sufficient to send messages.
> We should change the setup so we set the receive callback before we start the Server.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)