ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: Thin client failover mechanism (+ODBC, JDBC)
Date Fri, 02 Feb 2018 07:09:07 GMT
Dmitriy, yes, that's what I'm implementing as part of IGNITE-7282:
* List of hosts in config
* Pick random index (basic load balancing), connect
* When connection is lost, all current requests throw an exception
* Next request causes reconnect attempt to the next host
* If all hosts fail, throw exception

On Fri, Feb 2, 2018 at 12:44 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>

> On Thu, Feb 1, 2018 at 5:55 AM, Pavel Tupitsyn <ptupitsyn@apache.org>
> wrote:
> > Ok, let's add simple reconnect logic and see what will come of it.
> >
> Just to clarify, a list of IP addresses a client should connect to needs to
> be provided on startup. Once a connection is lost, a client needs to try to
> connect to all other IPs in the list before failing. Agree, this should be
> fairly simple to implement.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message