Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0.0-beta1
-
None
Description
Case: Query was canceled (for some reason, execution timeout or client side action) but coordinator failed with sending close message . Need to handle such a case and just ignore, no recovery actions are needed here, no errors on client side.
Let`s explain we have a long running query and for some reasons cancel is triggered, directly after two things are happen: 1. coordinator start to send close message into working nodes 2. one or more nodes become unavailable. On the basis of our assumptions - NodeLeft event need to be raised but it also can be raised after message service error. All such cases need to be handled correctly.