the Blog has issue's the code which is in public s3 bucket doesn't exist so the ec2 instance doesn't have to ignite at all I raised a concern with AWS Blog team, I will try community ami Ignite ec2 instance or try to install ignite on my own manually.
On Fri, Aug 9, 2019 at 11:20 AM sri hari kali charan Tummala < kali.tumm...@gmail.com> wrote: > please check. > > On Fri, Aug 9, 2019 at 10:58 AM sri hari kali charan Tummala < > kali.tumm...@gmail.com> wrote: > >> give me couple of minutes I think I opened 0 to 65000 ports for inbound >> thats it , if I have to open all these ports separately I have to give a >> try. >> >> On Fri, Aug 9, 2019 at 10:55 AM Himanshu Gupta <himanshu....@gmail.com> >> wrote: >> >>> Can you share screenshot of your inbound traffic setting, I think it >>> need to be something like this >>> >>> Example: >>> >>> Inbound: >>> Custom TCP Rule TCP 10800 - 10900 0.0.0.0/0 client >>> Custom TCP Rule TCP 47500 - 47600 0.0.0.0/0 discovery >>> Custom TCP Rule TCP 47100 - 47200 0.0.0.0/0 communication >>> >>> Outbound: >>> All traffic All All 0.0.0.0/0 >>> All traffic All All ::/0 >>> >>> as mentioned in >>> http://apache-ignite-users.70518.x6.nabble.com/AWS-Cluster-td23903.html >>> >>> On Fri, Aug 9, 2019 at 9:52 AM sri hari kali charan Tummala < >>> kali.tumm...@gmail.com> wrote: >>> >>>> yes, all traffic inbound and outbound (TCP), I am able to do ssh also I >>>> am able to ping public ip address from my laptop and the Ec2 instance is >>>> able to ping the www.amazon.com. >>>> >>>> >>>> >>>> On Fri, Aug 9, 2019 at 10:46 AM Himanshu Gupta <himanshu....@gmail.com> >>>> wrote: >>>> >>>>> Did you open the ports on EC2 at which your ignite cluster is running? >>>>> >>>>> On Fri, Aug 9, 2019 at 8:50 AM sri hari kali charan Tummala < >>>>> kali.tumm...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> thanks for replying I am following the below blog as per some expert >>>>>> suggestion he asked me to use my laptop ip address and elastic ip address >>>>>> of Ec2 instance ( >>>>>> https://github.com/aws-samples/aws-big-data-blog/blob/9eb7cc30a2dfb02c15252a5bad03603a21451572/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/src/main/java/com/amazon/dynamostreams/clientlibrary/StreamsToIgnite.properties#L4 >>>>>> ) >>>>>> >>>>>> >>>>>> https://aws.amazon.com/blogs/big-data/real-time-in-memory-oltp-and-analytics-with-apache-ignite-on-aws/ >>>>>> >>>>>> Correct me if wrong I will give a try. >>>>>> >>>>>> Thanks >>>>>> Sri >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Aug 9, 2019 at 8:27 AM Ilya Kasnacheev < >>>>>> ilya.kasnach...@gmail.com> wrote: >>>>>> >>>>>>> Hello! >>>>>>> >>>>>>> In my experience, on EC2 nodes usually use internal network to talk >>>>>>> to each other. They will advertise these to any nodes trying to connect, >>>>>>> which will cause issues. >>>>>>> >>>>>>> Is it an option for you to use some flavor of Thin Client to talk to >>>>>>> your cluster? We do not recommend having heterogenous, non-collocated >>>>>>> clusters, and this includes thick client nodes. >>>>>>> >>>>>>> Regards, >>>>>>> -- >>>>>>> Ilya Kasnacheev >>>>>>> >>>>>>> >>>>>>> пт, 9 авг. 2019 г. в 03:35, sri hari kali charan Tummala < >>>>>>> kali.tumm...@gmail.com>: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> I am trying to connect a ignite ec2 instance (one node) remotely >>>>>>>> from local PC Mac Intellij Idea I am using TcpDicoverySpi to connect >>>>>>>> ignite >>>>>>>> ec2 instance public IP but its failing to connect I did open all the >>>>>>>> ports >>>>>>>> I was able to do ssh and ping the host from my local PC even on the >>>>>>>> remote >>>>>>>> host I am able to access internet, ignite right now fails with below >>>>>>>> error. >>>>>>>> >>>>>>>> [20:14:54] Failed to connect to any address from IP finder (will >>>>>>>> retry to join topology every 2000 ms; change 'reconnectDelay' to >>>>>>>> configure >>>>>>>> the frequency of retries): [/52.204.222.254:47500, / >>>>>>>> 52.204.222.254:47501, /52.204.222.254:47502, /52.204.222.254:47503, >>>>>>>> /52.204.222.254:47504, /52.204.222.254:47505, /52.204.222.254:47506, >>>>>>>> /52.204.222.254:47507, /52.204.222.254:47508, /52.204.222.254:47509, >>>>>>>> /52.204.222.254:47510] >>>>>>>> >>>>>>>> I am following below blog , can any one help how to access ignite >>>>>>>> cluster which is setup remotely do I need to build my code and run in >>>>>>>> the >>>>>>>> cluster by ssh to the box ? >>>>>>>> >>>>>>>> >>>>>>>> https://aws.amazon.com/blogs/big-data/real-time-in-memory-oltp-and-analytics-with-apache-ignite-on-aws/ >>>>>>>> >>>>>>>> 4.222.254:47507, /52.204.222.254:47508, /52.204.222.254:47509, / >>>>>>>> 52.204.222.254:47510] >>>>>>>> >>>>>>>> [image: Thumbnail] >>>>>>>> <https://uploads.disquscdn.com/images/23e365052ba57ed2be6399b06c036ada661bc92584046760584c85afefe4a4e4.png> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks & Regards >>>>>>>> Sri Tummala >>>>>>>> >>>>>>>> >>>>>> >>>>>> -- >>>>>> Thanks & Regards >>>>>> Sri Tummala >>>>>> >>>>>> >>>> >>>> -- >>>> Thanks & Regards >>>> Sri Tummala >>>> >>>> >> >> -- >> Thanks & Regards >> Sri Tummala >> >> > > -- > Thanks & Regards > Sri Tummala > > -- Thanks & Regards Sri Tummala