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 09:16:59 GMT
Alexey, let's keep it simple for now.

On Fri, Feb 2, 2018 at 11:47 AM, Alexey Kuznetsov <akuznetsov@gridgain.com>
wrote:

> Pavel,
>
> Does it make sense in case of "connection lost" to ping available addresses
> in parallel?
> For example using thread pool of 4 threads?
> This may speed up detecting next alive node under Windows if several
> addresses become unavailable at once.
>
> On Fri, Feb 2, 2018 at 2:09 PM, Pavel Tupitsyn <ptupitsyn@apache.org>
> wrote:
>
> > 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>
> > wrote:
> >
> > > 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.
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

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