Vladimir Ozerov created IGNITE-4112:
---------------------------------------
Summary: Client is stopped if communication to servers is lost during (re)connect routine.
Key: IGNITE-4112
URL:
https://issues.apache.org/jira/browse/IGNITE-4112 Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Fix For: 1.8
Consider the following situation for the client which is currently disconnected:
1) Link to servers is restored;
2) Clients connects successfully;
3) Link is broken again after some time.
Result: client is disconnected.
But!
1) Link to servers is restored;
2) Clients is re-connecting;
3) Link is broken again before reconnect is finished.
Result: client might be stopped (for new client it will exit from {{Ignition.start}} routine with exception).
Apparently, we need to make (re)connect routine "atomic" with respect to concurrent network events. That is, we either reconnect all components successfully, or client is forcefully moved to disconnected state again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
