Re: How can we use the Discovery URL with SQLLINE which is both load balanced and Fault tolerent

[Nikolai Tikhonov]

Hi!

In current implementation thin driver doesn't support these features. You
can use thick driver [1] that supports them.

1. https://apacheignite.readme.io/docs/jdbc-driver#jdbc-client-node-driver

On Thu, Dec 7, 2017 at 6:28 PM, Naveen  wrote:

> Hi
>
> I am using 2.3, have 3 nodes in my cluster,
> This is how the config XML entries look like, all 3 nodes have below entry
>
>   
>  class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> 
>
>  class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.
> TcpDiscoveryVmIpFinder">
>
> 
> 
>
>  10.144.114.113:47500..
> 47502
>  10.144.114.114:47500..
> 47502
>  10.144.114.115:47500..
> 47502
> 
> 
> 
> 
> 
> 
>
> Client XML also has the same entry and along with that it also has
>  name="clientMode" value="true"/>
>
> So my cluster has 3 data nodes and one client node, my java clients connect
> connect to client node for all the operations. Is it the right way to do or
> any best practices we have.
>
> Also, thru sqlline, we normally give the URL like this
>
> jdbc:ignite:thin://10.144.114.113:10800
>
> ANd for some reason, if this node is down, I guess it wont be able to
> connect to the cluster.
> Can I give pair of nodes here like the below, so that it works in FT, if
> first one is down, requests goes to the second node etc.
>
> jdbc:ignite:thin://10.144.114.113:10800;10.144.114.114:10800;
> 10.144.114.115:10800
>
> Thanks
> Naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

How can we use the Discovery URL with SQLLINE which is both load balanced and Fault tolerent

[Naveen]

Hi

I am using 2.3, have 3 nodes in my cluster, 
This is how the config XML entries look like, all 3 nodes have below entry

  








 10.144.114.113:47500..47502
 10.144.114.114:47500..47502
 10.144.114.115:47500..47502







Client XML also has the same entry and along with that it also has 

So my cluster has 3 data nodes and one client node, my java clients connect
connect to client node for all the operations. Is it the right way to do or
any best practices we have.

Also, thru sqlline, we normally give the URL like this 

jdbc:ignite:thin://10.144.114.113:10800

ANd for some reason, if this node is down, I guess it wont be able to
connect to the cluster. 
Can I give pair of nodes here like the below, so that it works in FT, if
first one is down, requests goes to the second node etc.

jdbc:ignite:thin://10.144.114.113:10800;10.144.114.114:10800;10.144.114.115:10800

Thanks
Naveen



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/