ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Naveen <naveen.band...@gmail.com>
Subject How can we use the Discovery URL with SQLLINE which is both load balanced and Fault tolerent
Date Thu, 07 Dec 2017 15:28:25 GMT
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

      <property name="discoverySpi">
            <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    
                    <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                    
                        <property name="addresses">
                            <list>
                                
                                 <value>10.144.114.113:47500..47502</value>
                                 <value>10.144.114.114:47500..47502</value>
                                 <value>10.144.114.115:47500..47502</value>
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>

Client XML also has the same entry and along with that it also has <property
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/

Mime
View raw message