You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "shicheng31604@gmail.com" <sh...@gmail.com> on 2019/07/04 08:46:55 UTC
Distributed Cluster Deployment
Hi all:
The official documentation on the cluster building part seems to only mention TCP/IP and Zookeeper discovery, and the case is also implemented through the Spring project. I am more concerned about whether it is possible to build a distributed cluster directly?If so , how ?
shicheng31604@gmail.com
Re: Re: Distributed Cluster Deployment
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I think you can use sqlline.sh directly in the shell for distributed
queries either way: with Java and with XML.
Regards,
--
Ilya Kasnacheev
пн, 8 июл. 2019 г. в 04:27, shicheng31604@gmail.com <shicheng31604@gmail.com
>:
> You mean that I need to configure Ignite with Java code (call
> Ignition.start()) so that I can use sqlline.sh directly in the shell for
> distributed queries?
>
> ------------------------------
> shicheng31604@gmail.com
>
>
> *From:* Ilya Kasnacheev <il...@gmail.com>
> *Date:* 2019-07-05 19:51
> *To:* user <us...@ignite.apache.org>
> *Subject:* Re: Re: Distributed Cluster Deployment
> Hello!
>
> The easiest way to configure Ignite without external configuration is just
> issuing Ignition.start() in your Java code.
>
> It uses Multicast IP finder by default, so if you start several nodes in a
> single subnet they should join as a single distributed cluster.
>
> Then you can use sqlline to connect to any node.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 5 июл. 2019 г. в 03:44, shicheng31604@gmail.com <
> shicheng31604@gmail.com>:
>
>> Maybe I didn't describe it clearly. How to configure Ignite, you can
>> achieve distributed without external configuration, and then directly use
>> the sqline command to connect, for distributed query operations. Should it
>> be through the configuration file below the installation file? I see that
>> the configuration file that comes with it seems to be the format that
>> Spring requires. Is there any relation between the two?
>>
>> ------------------------------
>> shicheng31604@gmail.com
>>
>>
>> *From:* Vladimir Pligin <vo...@yandex.ru>
>> *Date:* 2019-07-04 20:27
>> *To:* user <us...@ignite.apache.org>
>> *Subject:* Re: Distributed Cluster Deployment
>> Hi,
>>
>> Spring here is just a convenient way of configuration building.
>> Ignite is not tightly bound to it. You're able to construct everything
>> programmatically.
>> For example here https://apacheignite.readme.io/docs/tcpip-discovery you
>> can
>> switch example from "XML" to "Java".
>> And Spring xml configuration
>> <bean class="org.apache.ignite.configuration.IgniteConfiguration">
>> ...
>> <property name="discoverySpi">
>> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>> <property name="ipFinder">
>> <bean
>>
>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
>> <property name="multicastGroup" value="228.10.10.157"/>
>> </bean>
>> </property>
>> </bean>
>> </property>
>> </bean>
>>
>> turns into
>>
>> TcpDiscoverySpi spi = new TcpDiscoverySpi();
>> TcpDiscoveryMulticastIpFinder ipFinder = new
>> TcpDiscoveryMulticastIpFinder();
>> ipFinder.setMulticastGroup("228.10.10.157");
>> spi.setIpFinder(ipFinder);
>> IgniteConfiguration cfg = new IgniteConfiguration();
>> cfg.setDiscoverySpi(spi);
>> Ignition.start(cfg);
>>
>> Does it make sense?
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>>
Re: Re: Distributed Cluster Deployment
Posted by "shicheng31604@gmail.com" <sh...@gmail.com>.
You mean that I need to configure Ignite with Java code (call Ignition.start()) so that I can use sqlline.sh directly in the shell for distributed queries?
shicheng31604@gmail.com
From: Ilya Kasnacheev
Date: 2019-07-05 19:51
To: user
Subject: Re: Re: Distributed Cluster Deployment
Hello!
The easiest way to configure Ignite without external configuration is just issuing Ignition.start() in your Java code.
It uses Multicast IP finder by default, so if you start several nodes in a single subnet they should join as a single distributed cluster.
Then you can use sqlline to connect to any node.
Regards,
--
Ilya Kasnacheev
пт, 5 июл. 2019 г. в 03:44, shicheng31604@gmail.com <sh...@gmail.com>:
Maybe I didn't describe it clearly. How to configure Ignite, you can achieve distributed without external configuration, and then directly use the sqline command to connect, for distributed query operations. Should it be through the configuration file below the installation file? I see that the configuration file that comes with it seems to be the format that Spring requires. Is there any relation between the two?
shicheng31604@gmail.com
From: Vladimir Pligin
Date: 2019-07-04 20:27
To: user
Subject: Re: Distributed Cluster Deployment
Hi,
Spring here is just a convenient way of configuration building.
Ignite is not tightly bound to it. You're able to construct everything
programmatically.
For example here https://apacheignite.readme.io/docs/tcpip-discovery you can
switch example from "XML" to "Java".
And Spring xml configuration
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
...
<property name="discoverySpi">
<bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
<property name="multicastGroup" value="228.10.10.157"/>
</bean>
</property>
</bean>
</property>
</bean>
turns into
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryMulticastIpFinder ipFinder = new
TcpDiscoveryMulticastIpFinder();
ipFinder.setMulticastGroup("228.10.10.157");
spi.setIpFinder(ipFinder);
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setDiscoverySpi(spi);
Ignition.start(cfg);
Does it make sense?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Re: Distributed Cluster Deployment
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
The easiest way to configure Ignite without external configuration is just
issuing Ignition.start() in your Java code.
It uses Multicast IP finder by default, so if you start several nodes in a
single subnet they should join as a single distributed cluster.
Then you can use sqlline to connect to any node.
Regards,
--
Ilya Kasnacheev
пт, 5 июл. 2019 г. в 03:44, shicheng31604@gmail.com <shicheng31604@gmail.com
>:
> Maybe I didn't describe it clearly. How to configure Ignite, you can
> achieve distributed without external configuration, and then directly use
> the sqline command to connect, for distributed query operations. Should it
> be through the configuration file below the installation file? I see that
> the configuration file that comes with it seems to be the format that
> Spring requires. Is there any relation between the two?
>
> ------------------------------
> shicheng31604@gmail.com
>
>
> *From:* Vladimir Pligin <vo...@yandex.ru>
> *Date:* 2019-07-04 20:27
> *To:* user <us...@ignite.apache.org>
> *Subject:* Re: Distributed Cluster Deployment
> Hi,
>
> Spring here is just a convenient way of configuration building.
> Ignite is not tightly bound to it. You're able to construct everything
> programmatically.
> For example here https://apacheignite.readme.io/docs/tcpip-discovery you
> can
> switch example from "XML" to "Java".
> And Spring xml configuration
> <bean class="org.apache.ignite.configuration.IgniteConfiguration">
> ...
> <property name="discoverySpi">
> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> <property name="ipFinder">
> <bean
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> <property name="multicastGroup" value="228.10.10.157"/>
> </bean>
> </property>
> </bean>
> </property>
> </bean>
>
> turns into
>
> TcpDiscoverySpi spi = new TcpDiscoverySpi();
> TcpDiscoveryMulticastIpFinder ipFinder = new
> TcpDiscoveryMulticastIpFinder();
> ipFinder.setMulticastGroup("228.10.10.157");
> spi.setIpFinder(ipFinder);
> IgniteConfiguration cfg = new IgniteConfiguration();
> cfg.setDiscoverySpi(spi);
> Ignition.start(cfg);
>
> Does it make sense?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
Re: Re: Distributed Cluster Deployment
Posted by "shicheng31604@gmail.com" <sh...@gmail.com>.
Maybe I didn't describe it clearly. How to configure Ignite, you can achieve distributed without external configuration, and then directly use the sqline command to connect, for distributed query operations. Should it be through the configuration file below the installation file? I see that the configuration file that comes with it seems to be the format that Spring requires. Is there any relation between the two?
shicheng31604@gmail.com
From: Vladimir Pligin
Date: 2019-07-04 20:27
To: user
Subject: Re: Distributed Cluster Deployment
Hi,
Spring here is just a convenient way of configuration building.
Ignite is not tightly bound to it. You're able to construct everything
programmatically.
For example here https://apacheignite.readme.io/docs/tcpip-discovery you can
switch example from "XML" to "Java".
And Spring xml configuration
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
...
<property name="discoverySpi">
<bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
<property name="multicastGroup" value="228.10.10.157"/>
</bean>
</property>
</bean>
</property>
</bean>
turns into
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryMulticastIpFinder ipFinder = new
TcpDiscoveryMulticastIpFinder();
ipFinder.setMulticastGroup("228.10.10.157");
spi.setIpFinder(ipFinder);
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setDiscoverySpi(spi);
Ignition.start(cfg);
Does it make sense?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Distributed Cluster Deployment
Posted by Vladimir Pligin <vo...@yandex.ru>.
Hi,
Spring here is just a convenient way of configuration building.
Ignite is not tightly bound to it. You're able to construct everything
programmatically.
For example here https://apacheignite.readme.io/docs/tcpip-discovery you can
switch example from "XML" to "Java".
And Spring xml configuration
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
...
<property name="discoverySpi">
<bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
<property name="multicastGroup" value="228.10.10.157"/>
</bean>
</property>
</bean>
</property>
</bean>
turns into
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryMulticastIpFinder ipFinder = new
TcpDiscoveryMulticastIpFinder();
ipFinder.setMulticastGroup("228.10.10.157");
spi.setIpFinder(ipFinder);
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setDiscoverySpi(spi);
Ignition.start(cfg);
Does it make sense?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/