[IGNITE-4112] Client is stopped if communication to servers is lost during (re)connect routine.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.7
• Fix Version/s: 2.0
• Component/s: general
• Assignee: Nikolay Tikhonov
• Reporter: Vladimir Ozerov
• Created: 26/Oct/16 15:03
• Updated: 03/Mar/17 12:49
• Resolved: 03/Mar/17 12:48

Description

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.

Issue Links

• is duplicated by: IGNITE-4473 Client should re-try connection attempt in case of concurrent network failure
• relates to: IGNITE-4473 Client should re-try connection attempt in case of concurrent network failure