Igniters, I'm working on client-side failover logic for .NET Thin Client. This will probably apply to ODBC and JDBC thin clients as well in future.
Currently all thin clients connect to a single specified Ignite node. The idea is to have multiple known nodes (host:port pairs) and reconnect to another node if current one goes down. Problems: - Protocol is stateful, server keeps track of query cursors for the session - Many operations are not idempotent, so retry is not an option - Async operations and multithreading are supported in .NET thin client So while we can detect socket connection failure and reconnect to a different node, all currently executing client operations and query cursors will still fail with an exception. I'm not sure how useful this behavior will be. Any thoughts, ideas? Thanks, Pavel
