Re: Does any one have working Ignite cluster on AWS
the package manager >>>> of the instance. >>>> >>>> $ sudo yum install java-1.8.0-openjdk.x86_64 >>>> >>>> Upload a GridGain distribution package into the instance. Run the >>>> following command from you local machine: >>>> >>>> $ scp -i privatekey.pem gridgain-community-8.7.6.zip >>>> scp://ec2-user@54.175.137.126 >>>> >>>> Login to the instance again and unpack the package: >>>> >>>> $ unzip gridgain-community-8.7.6.zip >>>> >>>> If you are going to connect to the cluster via REST API or use Web >>>> Console >>>> <https://www.gridgain.com/docs/web-console/latest/web-console-getting-started> >>>> , enable the 'ignite-rest-http' module >>>> <https://www.gridgain.com/docs/latest/developers-guide/setup#enabling-modules> >>>> . >>>> >>>> $ cp -r gridgain-community-8.7.6/libs/optional/ignite-rest-http/ >>>> gridgain-community-8.7.6/libs/ >>>> >>>> Repeat the above steps for the second instance. Now we are ready to >>>> configure the cluster nodes. >>>> >>>> >>>> Thanks >>>> >>>> Sri >>>> >>>> >>>> >>>> >>>> On Wed, Oct 16, 2019 at 9:18 AM sri hari kali charan Tummala < >>>> kali.tumm...@gmail.com> wrote: >>>> >>>>> Hi , >>>>> >>>>> someone sent me this I will give a try. >>>>> >>>>> >>>>> https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 >>>>> >>>>> Thanks >>>>> Sri >>>>> >>>>> On Wed, Oct 16, 2019 at 12:26 AM Muhammed Favas < >>>>> favas.muham...@expeedsoftware.com> wrote: >>>>> >>>>>> Hi Sri, >>>>>> >>>>>> >>>>>> >>>>>> For Question 1 >>>>>> >>>>>> In the ignite config file you use to launch ignite, >>>>>> you can give list of IP’s like below. The same config file should be >>>>>> placed >>>>>> in all the Ec2 servers. Once it is done, you can start ignite by using >>>>>> command $IGNITE_HOME/bin.ignite.sh. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> "org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder" >>>>>> > >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> IP1 >>>>>> >>>>>> IP2 >>>>>> >>>>>> IP3 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> For Question 2 >>>>>> >>>>>> In this approach, you don’t need to give the list of >>>>>> IP’s in ignite config file, instead you just have to create an s3 bucket >>>>>> and mention the s3 bucket name and access key in the ignite config. See >>>>>> below. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> "org.apache.ig
Re: Does any one have working Ignite cluster on AWS
k.x86_64 > > Upload a GridGain distribution package into the instance. Run the following > command from you local machine: > > $ scp -i privatekey.pem gridgain-community-8.7.6.zip > scp://ec2-user@54.175.137.126 <mailto:ec2-user@54.175.137.126> > Login to the instance again and unpack the package: > > $ unzip gridgain-community-8.7.6.zip > > If you are going to connect to the cluster via REST API or use Web Console > <https://www.gridgain.com/docs/web-console/latest/web-console-getting-started>, > enable the 'ignite-rest-http' module > <https://www.gridgain.com/docs/latest/developers-guide/setup#enabling-modules>. > > $ cp -r gridgain-community-8.7.6/libs/optional/ignite-rest-http/ > gridgain-community-8.7.6/libs/ > > Repeat the above steps for the second instance. Now we are ready to configure > the cluster nodes. > > > > Thanks > > Sri > > > > > > On Wed, Oct 16, 2019 at 9:18 AM sri hari kali charan Tummala > mailto:kali.tumm...@gmail.com>> wrote: > Hi , > > someone sent me this I will give a try. > > https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 > <https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2> > > Thanks > Sri > > On Wed, Oct 16, 2019 at 12:26 AM Muhammed Favas > <mailto:favas.muham...@expeedsoftware.com>> wrote: > Hi Sri, > > > > For Question 1 > > In the ignite config file you use to launch ignite, you can > give list of IP’s like below. The same config file should be placed in all > the Ec2 servers. Once it is done, you can start ignite by using command > $IGNITE_HOME/bin.ignite.sh <http://bin.ignite.sh/>. > > > > > > > > > > > > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > > > > > IP1 > > IP2 > > IP3 > > > > > > > > > > > > > > > > > > For Question 2 > > In this approach, you don’t need to give the list of IP’s in > ignite config file, instead you just have to create an s3 bucket and mention > the s3 bucket name and access key in the ignite config. See below. > > > > > > > > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> > > > > > > > > > > > > > > > > > > > > > > > > > > Hope it will help you > > > > Regards, > > Favas > > > > From: Denis Magda mailto:dma...@apache.org>> > Sent: Tuesday, October 15, 2019 11:21 PM > To: user@ignite.apache.org <mailto:user@ignite.apache.org> > Subject: Re: Does any one have working Ignite cluster on AWS > > > > Refer to GridGain documentation: > https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 > <https://www.gridgain.com/docs/8.7.6/installation-guide/manual-install-on-ec2> > > > Just swap GridGain with Ignite artifacts, the rest is identical. > > > > - > > Denis > > > > > > On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala > mailto:kali.tumm...@gmail.com>> wrote: > > documentation is not covering step by step it's not that helpful. > > > > On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev <mailto:ilya.kasnach...@gmail.com>> wrote: > > Hello! > > > > Please refer to the docs: > > > > https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder > <https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder> > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala > mailto:kali.tumm...@gmail.com>>: > > thanks for repl
Re: Does any one have working Ignite cluster on AWS
from you local machine: >>> >>> $ scp -i privatekey.pem gridgain-community-8.7.6.zip >>> scp://ec2-user@54.175.137.126 >>> >>> Login to the instance again and unpack the package: >>> >>> $ unzip gridgain-community-8.7.6.zip >>> >>> If you are going to connect to the cluster via REST API or use Web >>> Console >>> <https://www.gridgain.com/docs/web-console/latest/web-console-getting-started> >>> , enable the 'ignite-rest-http' module >>> <https://www.gridgain.com/docs/latest/developers-guide/setup#enabling-modules> >>> . >>> >>> $ cp -r gridgain-community-8.7.6/libs/optional/ignite-rest-http/ >>> gridgain-community-8.7.6/libs/ >>> >>> Repeat the above steps for the second instance. Now we are ready to >>> configure the cluster nodes. >>> >>> >>> Thanks >>> >>> Sri >>> >>> >>> >>> >>> On Wed, Oct 16, 2019 at 9:18 AM sri hari kali charan Tummala < >>> kali.tumm...@gmail.com> wrote: >>> >>>> Hi , >>>> >>>> someone sent me this I will give a try. >>>> >>>> >>>> https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 >>>> >>>> Thanks >>>> Sri >>>> >>>> On Wed, Oct 16, 2019 at 12:26 AM Muhammed Favas < >>>> favas.muham...@expeedsoftware.com> wrote: >>>> >>>>> Hi Sri, >>>>> >>>>> >>>>> >>>>> For Question 1 >>>>> >>>>> In the ignite config file you use to launch ignite, >>>>> you can give list of IP’s like below. The same config file should be >>>>> placed >>>>> in all the Ec2 servers. Once it is done, you can start ignite by using >>>>> command $IGNITE_HOME/bin.ignite.sh. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> "org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder" >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> IP1 >>>>> >>>>> IP2 >>>>> >>>>> IP3 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> For Question 2 >>>>> >>>>> In this approach, you don’t need to give the list of >>>>> IP’s in ignite config file, instead you just have to create an s3 bucket >>>>> and mention the s3 bucket name and access key in the ignite config. See >>>>> below. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>>> >>>>> >>>>> >>>>> >>>> "org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder" >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> "com.amazonaws.auth.BasicAWSCredentials"> >>>>> >>>>> >>>>> >>>>> >>>> /> >>>>> >>>>&g
Re: Does any one have working Ignite cluster on AWS
tall-on-ec2 >>> >>> Thanks >>> Sri >>> >>> On Wed, Oct 16, 2019 at 12:26 AM Muhammed Favas < >>> favas.muham...@expeedsoftware.com> wrote: >>> >>>> Hi Sri, >>>> >>>> >>>> >>>> For Question 1 >>>> >>>> In the ignite config file you use to launch ignite, you >>>> can give list of IP’s like below. The same config file should be placed in >>>> all the Ec2 servers. Once it is done, you can start ignite by using command >>>> $IGNITE_HOME/bin.ignite.sh. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>> >>>> >>>> >>>> >>>> >>>> >>> "org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder" >>>> > >>>> >>>> >>>> >>>> >>>> >>>> IP1 >>>> >>>> IP2 >>>> >>>> IP3 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> For Question 2 >>>> >>>> In this approach, you don’t need to give the list of >>>> IP’s in ignite config file, instead you just have to create an s3 bucket >>>> and mention the s3 bucket name and access key in the ignite config. See >>>> below. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>> >>>> >>>> >>>> >>> "org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder" >>>> > >>>> >>>> >>>> >>>> >>>> >>>> >>> "com.amazonaws.auth.BasicAWSCredentials"> >>>> >>>> >>>> >>>> >>> /> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Hope it will help you >>>> >>>> >>>> >>>> *Regards,* >>>> >>>> *Favas * >>>> >>>> >>>> >>>> *From:* Denis Magda >>>> *Sent:* Tuesday, October 15, 2019 11:21 PM >>>> *To:* user@ignite.apache.org >>>> *Subject:* Re: Does any one have working Ignite cluster on AWS >>>> >>>> >>>> >>>> Refer to GridGain documentation: >>>> https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 >>>> <https://www.gridgain.com/docs/8.7.6/installation-guide/manual-install-on-ec2> >>>> >>>> >>>> >>>> Just swap GridGain with Ignite artifacts, the rest is identical. >>>> >>>> >>>> - >>>> >>>> Denis >>>> >>>> >>>> >>>> >>>> >>>> On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala < >>>> kali.tumm...@gmail.com> wrote: >>>> >>>> documentation is not covering step by step it's not that helpful. >>>> >>>> >>>> >>>> On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev < >>>> ilya.kasnach...@gmail.com> wrote: >>>> >>>> Hello! >>>> >>>> >>>> >>>> Please refer to the docs: >>>> >>>> >>>> >>>> >>>> https://apacheignite.readme.io/docs/tcpip-discovery#section-s
Re: Does any one have working Ignite cluster on AWS
also can you send me full config file? so I dont have any typos etc IP1 IP2 IP3 For Question 2 In this approach, you don’t need to give the list of IP’s in ignite config file, instead you just have to create an s3 bucket and mention the s3 bucket name and access key in the ignite config. See below. On Wed, Oct 16, 2019 at 9:18 AM sri hari kali charan Tummala < kali.tumm...@gmail.com> wrote: > Hi , > > someone sent me this I will give a try. > > > https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 > > Thanks > Sri > > On Wed, Oct 16, 2019 at 12:26 AM Muhammed Favas < > favas.muham...@expeedsoftware.com> wrote: > >> Hi Sri, >> >> >> >> For Question 1 >> >> In the ignite config file you use to launch ignite, you >> can give list of IP’s like below. The same config file should be placed in >> all the Ec2 servers. Once it is done, you can start ignite by using command >> $IGNITE_HOME/bin.ignite.sh. >> >> >> >> >> >> >> >> >> >> >> > "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >> >> >> >> >> >> > "org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >> >> >> >> >> >> IP1 >> >> IP2 >> >> IP3 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> For Question 2 >> >> In this approach, you don’t need to give the list of IP’s >> in ignite config file, instead you just have to create an s3 bucket and >> mention the s3 bucket name and access key in the ignite config. See below. >> >> >> >> >> >> >> >> > > >> >> >> >> > "org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> >> >> > /> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Hope it will help you >> >> >> >> *Regards,* >> >> *Favas * >> >> >> >> *From:* Denis Magda >> *Sent:* Tuesday, October 15, 2019 11:21 PM >> *To:* user@ignite.apache.org >> *Subject:* Re: Does any one have working Ignite cluster on AWS >> >> >> >> Refer to GridGain documentation: >> https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 >> <https://www.gridgain.com/docs/8.7.6/installation-guide/manual-install-on-ec2> >> >> >> >> Just swap GridGain with Ignite artifacts, the rest is identical. >> >> >> - >> >> Denis >> >> >> >> >> >> On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala < >> kali.tumm...@gmail.com> wrote: >> >> documentation is not covering step by step it's not that helpful. >> >> >> >> On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev < >> ilya.kasnach...@gmail.com> wrote: >> >> Hello! >> >> >> >> Please refer to the docs: >> >> >> >> >> https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder >> >> >> >> Regards, >> >> -- >> >> Ilya Kasnac
Re: Does any one have working Ignite cluster on AWS
Hi , someone sent me this I will give a try. https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 Thanks Sri On Wed, Oct 16, 2019 at 12:26 AM Muhammed Favas < favas.muham...@expeedsoftware.com> wrote: > Hi Sri, > > > > For Question 1 > > In the ignite config file you use to launch ignite, you > can give list of IP’s like below. The same config file should be placed in > all the Ec2 servers. Once it is done, you can start ignite by using command > $IGNITE_HOME/bin.ignite.sh. > > > > > > > > > > > "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> > > > > > > "org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > > > > > IP1 > > IP2 > > IP3 > > > > > > > > > > > > > > > > > > For Question 2 > > In this approach, you don’t need to give the list of IP’s > in ignite config file, instead you just have to create an s3 bucket and > mention the s3 bucket name and access key in the ignite config. See below. > > > > > > > > > > > > "org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> > > /> > > > > > > > > > > > > > > > > > > > > > > > > Hope it will help you > > > > *Regards,* > > *Favas * > > > > *From:* Denis Magda > *Sent:* Tuesday, October 15, 2019 11:21 PM > *To:* user@ignite.apache.org > *Subject:* Re: Does any one have working Ignite cluster on AWS > > > > Refer to GridGain documentation: > https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 > <https://www.gridgain.com/docs/8.7.6/installation-guide/manual-install-on-ec2> > > > > Just swap GridGain with Ignite artifacts, the rest is identical. > > > - > > Denis > > > > > > On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala < > kali.tumm...@gmail.com> wrote: > > documentation is not covering step by step it's not that helpful. > > > > On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> wrote: > > Hello! > > > > Please refer to the docs: > > > > > https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala < > kali.tumm...@gmail.com>: > > thanks for replying but sorry not getting it please dumb it down, below > are my questions. > > > > Statically giving the public IP list in the IP configuration section in > ignite config file. > > Question:- wherein the config file should I give the IP address, imagine I > launch 3 ec2 instances with public IP should I create a file in S3 bucket > with file containing IP address of ec2 instance? > > > > Use s3 bucket to configure the IP, and it will automatically discover the > related nodes from s3 bucket. > > Question:- ok I will give the s3 bucket name does the bucket need to have > a file containing IP address or just empty bucket? > > > > T > <https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json> > hanks > > Sri > > > > On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas < > favas.muham...@expeedsoftware.com> wrote: > > Hi Sri, > > > > If your nodes created in EC2, it is very simple to start the ignite > cluster. You have two option to configure the IP for all nodes auto > discover the IP. > >1. Statically giving the public IP list in the IP configuration >section in ignite config file. >2. Use s3 bucket to configure the IP, and it will automatically > discover the related nodes from s3 bucket. > > > > I am using the 2nd method, and below is the configuration I have given > for my cluster > > > > >
RE: Does any one have working Ignite cluster on AWS
Hi Sri, For Question 1 In the ignite config file you use to launch ignite, you can give list of IP’s like below. The same config file should be placed in all the Ec2 servers. Once it is done, you can start ignite by using command $IGNITE_HOME/bin.ignite.sh. IP1 IP2 IP3 For Question 2 In this approach, you don’t need to give the list of IP’s in ignite config file, instead you just have to create an s3 bucket and mention the s3 bucket name and access key in the ignite config. See below. Hope it will help you Regards, Favas From: Denis Magda Sent: Tuesday, October 15, 2019 11:21 PM To: user@ignite.apache.org Subject: Re: Does any one have working Ignite cluster on AWS Refer to GridGain documentation: https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2<https://www.gridgain.com/docs/8.7.6/installation-guide/manual-install-on-ec2> Just swap GridGain with Ignite artifacts, the rest is identical. - Denis On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala mailto:kali.tumm...@gmail.com>> wrote: documentation is not covering step by step it's not that helpful. On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev mailto:ilya.kasnach...@gmail.com>> wrote: Hello! Please refer to the docs: https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder Regards, -- Ilya Kasnacheev пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala mailto:kali.tumm...@gmail.com>>: thanks for replying but sorry not getting it please dumb it down, below are my questions. Statically giving the public IP list in the IP configuration section in ignite config file. Question:- wherein the config file should I give the IP address, imagine I launch 3 ec2 instances with public IP should I create a file in S3 bucket with file containing IP address of ec2 instance? Use s3 bucket to configure the IP, and it will automatically discover the related nodes from s3 bucket. Question:- ok I will give the s3 bucket name does the bucket need to have a file containing IP address or just empty bucket? T<https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json>hanks Sri On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas mailto:favas.muham...@expeedsoftware.com>> wrote: Hi Sri, If your nodes created in EC2, it is very simple to start the ignite cluster. You have two option to configure the IP for all nodes auto discover the IP. 1. Statically giving the public IP list in the IP configuration section in ignite config file. 2. Use s3 bucket to configure the IP, and it will automatically discover the related nodes from s3 bucket. I am using the 2nd method, and below is the configuration I have given for my cluster Regards, Favas From: sri hari kali charan Tummala mailto:kali.tumm...@gmail.com>> Sent: Friday, September 27, 2019 10:02 PM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Does any one have working Ignite cluster on AWS Hi All, can someone help me run a working ignite cuter on AWS , did anyone able to figure out steps required for setting up working ignite cluster on AWS. Ignite documentation doesnt make sense it's just launching a docker instance on Ec2. -- Thanks & Regards Sri Tummala -- Thanks & Regards Sri Tummala -- Thanks & Regards Sri Tummala
Re: Does any one have working Ignite cluster on AWS
Refer to GridGain documentation: https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2 Just swap GridGain with Ignite artifacts, the rest is identical. - Denis On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala < kali.tumm...@gmail.com> wrote: > documentation is not covering step by step it's not that helpful. > > On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> wrote: > >> Hello! >> >> Please refer to the docs: >> >> >> https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala < >> kali.tumm...@gmail.com>: >> >>> thanks for replying but sorry not getting it please dumb it down, below >>> are my questions. >>> >>> Statically giving the public IP list in the IP configuration section in >>> ignite config file. >>> Question:- wherein the config file should I give the IP address, imagine >>> I launch 3 ec2 instances with public IP should I create a file in S3 bucket >>> with file containing IP address of ec2 instance? >>> >>> Use s3 bucket to configure the IP, and it will automatically discover >>> the related nodes from s3 bucket. >>> Question:- ok I will give the s3 bucket name does the bucket need to >>> have a file containing IP address or just empty bucket? >>> >>> T >>> <https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json> >>> hanks >>> Sri >>> >>> On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas < >>> favas.muham...@expeedsoftware.com> wrote: >>> >>>> Hi Sri, >>>> >>>> >>>> >>>> If your nodes created in EC2, it is very simple to start the ignite >>>> cluster. You have two option to configure the IP for all nodes auto >>>> discover the IP. >>>> >>>>1. Statically giving the public IP list in the IP configuration >>>>section in ignite config file. >>>>2. Use s3 bucket to configure the IP, and it will automatically >>>>discover the related nodes from s3 bucket. >>>> >>>> >>>> >>>> I am using the 2nd method, and below is the configuration I have given >>>> for my cluster >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>> >>>> >>>> >>>> >>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> >>>> >>>> >>>> >>>> >>>> >>>> >>> class="com.amazonaws.auth.BasicAWSCredentials"> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *Regards,* >>>> >>>> *Favas * >>>> >>>> >>>> >>>> *From:* sri hari kali charan Tummala >>>> *Sent:* Friday, September 27, 2019 10:02 PM >>>> *To:* user@ignite.apache.org >>>> *Subject:* Does any one have working Ignite cluster on AWS >>>> >>>> >>>> >>>> Hi All, >>>> >>>> >>>> >>>> can someone help me run a working ignite cuter on AWS , did anyone able >>>> to figure out steps required for setting up working ignite cluster on AWS. >>>> >>>> >>>> >>>> Ignite documentation doesnt make sense it's just launching a docker >>>> instance on Ec2. >>>> >>>> >>>> >>>> -- >>>> >>>> Thanks & Regards >>>> >>>> Sri Tummala >>>> >>>> >>>> >>> >>> >>> -- >>> Thanks & Regards >>> Sri Tummala >>> >>> > > -- > Thanks & Regards > Sri Tummala > >
Re: Does any one have working Ignite cluster on AWS
documentation is not covering step by step it's not that helpful. On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev wrote: > Hello! > > Please refer to the docs: > > > https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder > > Regards, > -- > Ilya Kasnacheev > > > пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala < > kali.tumm...@gmail.com>: > >> thanks for replying but sorry not getting it please dumb it down, below >> are my questions. >> >> Statically giving the public IP list in the IP configuration section in >> ignite config file. >> Question:- wherein the config file should I give the IP address, imagine >> I launch 3 ec2 instances with public IP should I create a file in S3 bucket >> with file containing IP address of ec2 instance? >> >> Use s3 bucket to configure the IP, and it will automatically discover the >> related nodes from s3 bucket. >> Question:- ok I will give the s3 bucket name does the bucket need to have >> a file containing IP address or just empty bucket? >> >> T >> <https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json> >> hanks >> Sri >> >> On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas < >> favas.muham...@expeedsoftware.com> wrote: >> >>> Hi Sri, >>> >>> >>> >>> If your nodes created in EC2, it is very simple to start the ignite >>> cluster. You have two option to configure the IP for all nodes auto >>> discover the IP. >>> >>>1. Statically giving the public IP list in the IP configuration >>>section in ignite config file. >>>2. Use s3 bucket to configure the IP, and it will automatically >>>discover the related nodes from s3 bucket. >>> >>> >>> >>> I am using the 2nd method, and below is the configuration I have given >>> for my cluster >>> >>> >>> >>> >>> >>> >>> >>> >> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>> >>> >>> >>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *Regards,* >>> >>> *Favas * >>> >>> >>> >>> *From:* sri hari kali charan Tummala >>> *Sent:* Friday, September 27, 2019 10:02 PM >>> *To:* user@ignite.apache.org >>> *Subject:* Does any one have working Ignite cluster on AWS >>> >>> >>> >>> Hi All, >>> >>> >>> >>> can someone help me run a working ignite cuter on AWS , did anyone able >>> to figure out steps required for setting up working ignite cluster on AWS. >>> >>> >>> >>> Ignite documentation doesnt make sense it's just launching a docker >>> instance on Ec2. >>> >>> >>> >>> -- >>> >>> Thanks & Regards >>> >>> Sri Tummala >>> >>> >>> >> >> >> -- >> Thanks & Regards >> Sri Tummala >> >> -- Thanks & Regards Sri Tummala
Re: Does any one have working Ignite cluster on AWS
Hello! Please refer to the docs: https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder Regards, -- Ilya Kasnacheev пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala < kali.tumm...@gmail.com>: > thanks for replying but sorry not getting it please dumb it down, below > are my questions. > > Statically giving the public IP list in the IP configuration section in > ignite config file. > Question:- wherein the config file should I give the IP address, imagine I > launch 3 ec2 instances with public IP should I create a file in S3 bucket > with file containing IP address of ec2 instance? > > Use s3 bucket to configure the IP, and it will automatically discover the > related nodes from s3 bucket. > Question:- ok I will give the s3 bucket name does the bucket need to have > a file containing IP address or just empty bucket? > > T > <https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json> > hanks > Sri > > On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas < > favas.muham...@expeedsoftware.com> wrote: > >> Hi Sri, >> >> >> >> If your nodes created in EC2, it is very simple to start the ignite >> cluster. You have two option to configure the IP for all nodes auto >> discover the IP. >> >>1. Statically giving the public IP list in the IP configuration >>section in ignite config file. >>2. Use s3 bucket to configure the IP, and it will automatically >>discover the related nodes from s3 bucket. >> >> >> >> I am using the 2nd method, and below is the configuration I have given >> for my cluster >> >> >> >> >> >> >> >> >> >> >> >> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Regards,* >> >> *Favas * >> >> >> >> *From:* sri hari kali charan Tummala >> *Sent:* Friday, September 27, 2019 10:02 PM >> *To:* user@ignite.apache.org >> *Subject:* Does any one have working Ignite cluster on AWS >> >> >> >> Hi All, >> >> >> >> can someone help me run a working ignite cuter on AWS , did anyone able >> to figure out steps required for setting up working ignite cluster on AWS. >> >> >> >> Ignite documentation doesnt make sense it's just launching a docker >> instance on Ec2. >> >> >> >> -- >> >> Thanks & Regards >> >> Sri Tummala >> >> >> > > > -- > Thanks & Regards > Sri Tummala > >
Re: Does any one have working Ignite cluster on AWS
thanks for replying but sorry not getting it please dumb it down, below are my questions. Statically giving the public IP list in the IP configuration section in ignite config file. Question:- wherein the config file should I give the IP address, imagine I launch 3 ec2 instances with public IP should I create a file in S3 bucket with file containing IP address of ec2 instance? Use s3 bucket to configure the IP, and it will automatically discover the related nodes from s3 bucket. Question:- ok I will give the s3 bucket name does the bucket need to have a file containing IP address or just empty bucket? T <https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json> hanks Sri On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas < favas.muham...@expeedsoftware.com> wrote: > Hi Sri, > > > > If your nodes created in EC2, it is very simple to start the ignite > cluster. You have two option to configure the IP for all nodes auto > discover the IP. > >1. Statically giving the public IP list in the IP configuration >section in ignite config file. >2. Use s3 bucket to configure the IP, and it will automatically >discover the related nodes from s3 bucket. > > > > I am using the 2nd method, and below is the configuration I have given > for my cluster > > > > > > > > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > *Regards,* > > *Favas * > > > > *From:* sri hari kali charan Tummala > *Sent:* Friday, September 27, 2019 10:02 PM > *To:* user@ignite.apache.org > *Subject:* Does any one have working Ignite cluster on AWS > > > > Hi All, > > > > can someone help me run a working ignite cuter on AWS , did anyone able to > figure out steps required for setting up working ignite cluster on AWS. > > > > Ignite documentation doesnt make sense it's just launching a docker > instance on Ec2. > > > > -- > > Thanks & Regards > > Sri Tummala > > > -- Thanks & Regards Sri Tummala
RE: Does any one have working Ignite cluster on AWS
Hi Sri, If your nodes created in EC2, it is very simple to start the ignite cluster. You have two option to configure the IP for all nodes auto discover the IP. 1. Statically giving the public IP list in the IP configuration section in ignite config file. 2. Use s3 bucket to configure the IP, and it will automatically discover the related nodes from s3 bucket. I am using the 2nd method, and below is the configuration I have given for my cluster Regards, Favas From: sri hari kali charan Tummala Sent: Friday, September 27, 2019 10:02 PM To: user@ignite.apache.org Subject: Does any one have working Ignite cluster on AWS Hi All, can someone help me run a working ignite cuter on AWS , did anyone able to figure out steps required for setting up working ignite cluster on AWS. Ignite documentation doesnt make sense it's just launching a docker instance on Ec2. -- Thanks & Regards Sri Tummala
Does any one have working Ignite cluster on AWS
Hi All, can someone help me run a working ignite cuter on AWS , did anyone able to figure out steps required for setting up working ignite cluster on AWS. Ignite documentation doesnt make sense it's just launching a docker instance on Ec2. -- Thanks & Regards Sri Tummala
