You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "unable to create messenger" IOException occurs in different scenarios. One of the scenarions is when
an instance is killed. before instance B can know that the instance A has been killed, it tries to send a
message via ClusterManager.send() (could be to sync the DSC or for some other reason).
When such an IOException occurs, the Shoal code should check which instance is supposedly down. Then
the code wait for a little while before finding the state that that instance is in. If the state is
alive/aliveandready, the message should be sent again as a retry. If the instance is in in_retry_mode (i.e. it
has'nt been deemed in_doubt/failed yet), then the right way of dealing with this should be decided.
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered:
The "unable to create messenger" IOException occurs in different scenarios. One of the scenarions is when
an instance is killed. before instance B can know that the instance A has been killed, it tries to send a
message via ClusterManager.send() (could be to sync the DSC or for some other reason).
When such an IOException occurs, the Shoal code should check which instance is supposedly down. Then
the code wait for a little while before finding the state that that instance is in. If the state is
alive/aliveandready, the message should be sent again as a retry. If the instance is in in_retry_mode (i.e. it
has'nt been deemed in_doubt/failed yet), then the right way of dealing with this should be decided.
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered: