Handle Ignite client node's connection issues (rare edge-cases)

[junaidzm13]

Feature Request

Description of Problem:

It is possible (although rare) that the Ignite client node gets disconnected from the Ignite cluster. In that case, although it will try reconnecting automatically by default, any cache queries while client tries reestablishing the connection will throw exception.

We should try handling those exceptions in a graceful manner and possibly make UI reflect this state to the users.

reference: https://ignite.apache.org/docs/latest/clustering/connect-client-nodes

Another edge-case to think about is what happens when the Ignite server itself goes down or gets restarted? Preliminary tests on my local env have shown that the client will not be able to establish a new connection automatically. What this means is with our current setup we'd have to restart the VUU server every time to have the Ignite's client node connect to the cluster.

https://stackoverflow.com/questions/64489779/apache-ignite-caches-unusable-after-reconnecting-to-ignite-servers