From user-return-26834-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Aug 9 18:23:54 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id CAB0C18063F for ; Fri, 9 Aug 2019 20:23:53 +0200 (CEST) Received: (qmail 81516 invoked by uid 500); 9 Aug 2019 18:23:52 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 81506 invoked by uid 99); 9 Aug 2019 18:23:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2019 18:23:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 04EA6C1D07 for ; Fri, 9 Aug 2019 18:23:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.816 X-Spam-Level: *** X-Spam-Status: No, score=3.816 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=2, KAM_BADIPHTTP=2, KAM_SHORT=0.001, NORMAL_HTTP_TO_IP=0.001, NUMERIC_HTTP_ADDR=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id X_FzgfhM6KCV for ; Fri, 9 Aug 2019 18:23:49 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.210.44; helo=mail-ot1-f44.google.com; envelope-from=himanshu.iit@gmail.com; receiver= Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 5F2B8BC808 for ; Fri, 9 Aug 2019 18:23:49 +0000 (UTC) Received: by mail-ot1-f44.google.com with SMTP id d17so136251057oth.5 for ; Fri, 09 Aug 2019 11:23:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GTPFRy73mkccMOmOOZIyL5qulOyhnpRqWMIZ6bt/XA0=; b=aDc/mHzfoS/0l65mzt4SaWsLh70+pHWyOpNKxlRrdEex4FihECa5m8t5d/uD4V+T9m I5f9x8xmYj/uiDQ6/eI2Du5rG2QzdI5r1OwrykAJLcJbHvirV1WthOnVaTz2L7kJwdIR 0NhzdgGOFbEP3LLTiCF5LST/hBEI3h8/QreK6s9gKsCjJMrACAT0nUIATlu8XQHt229v 4GGUdCdS0FboMl/3t9ogqiPrC3C9efuid2qlsDXmDnkyZ1swHhwaAFJHuQaqai+kW8QZ AmNDAf/nyX2XRiYyn2O0IyKeqWuJFcMcHfTDYv8jN2l2XSP8bLcLqltMgZOpNe8RX6Q9 +Pdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GTPFRy73mkccMOmOOZIyL5qulOyhnpRqWMIZ6bt/XA0=; b=F+L1PueoIp6r+S+DeLcHxo1MlB+nlt0dSKQ06V5Te4MMo1IdwzS5b2ngY7RpKC0TzJ yuwzTGhy1dmgHN2Vd3Mkh7EceOEnKWe8AM0jqPPyMiOc68SAD2g9t+nu7BgV62D5Bu7g CJATRP5X7Mk/CTzB0Me6Y37BSzZpuymt7dMjBCGgWjYrETio6062W+EsoenisWJ8Lmzs +O/eKyEx1r/JA29ImoIbj0w9keg8OBaIB8gp1izkl5sGEttK/OuyWj4CFB/YgLTTQW2Q 5dxCHW8BypJI5bWGKvWIAebYYu40g2Zge8dNx/QOnaVC+Dy9H1SbCao0LzS/bIAxBdtD 5OnA== X-Gm-Message-State: APjAAAULOSUELBNa6Z/oySapRDaIWD9Km7jXzsLHOBPwD8nX9QmhftVm qGH0T4gGqMTKKN8Bws3tFu/ZGAvdq+Y4t76n/aE= X-Google-Smtp-Source: APXvYqxAKWfKRF1AFoknU00rA8JbJo9mg3uJ/JXzEl6AfDcl0i3kiD/SMkO508gGcEJ1+PHd1q6LN3QNhB+i1qNXjG0= X-Received: by 2002:a6b:7e45:: with SMTP id k5mr15454481ioq.178.1565375028504; Fri, 09 Aug 2019 11:23:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Himanshu Gupta Date: Fri, 9 Aug 2019 13:23:37 -0500 Message-ID: Subject: Re: Unable to access Ignite Ec2 Instance from Local PC To: sri hari kali charan Tummala Cc: user@ignite.apache.org Content-Type: multipart/alternative; boundary="00000000000083adb5058fb346d4" --00000000000083adb5058fb346d4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry for late response , your configuration looks correct. I hope community ami will solve the problem. -Himanshu On Fri, Aug 9, 2019 at 11:07 AM sri hari kali charan Tummala < kali.tummala@gmail.com> wrote: > 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.tummala@gmail.com> wrote: > >> please check. >> >> On Fri, Aug 9, 2019 at 10:58 AM sri hari kali charan Tummala < >> kali.tummala@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 >>> 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.htm= l >>>> >>>> On Fri, Aug 9, 2019 at 9:52 AM sri hari kali charan Tummala < >>>> kali.tummala@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 instan= ce is >>>>> able to ping the www.amazon.com. >>>>> >>>>> >>>>> >>>>> On Fri, Aug 9, 2019 at 10:46 AM Himanshu Gupta >>>>> wrote: >>>>> >>>>>> Did you open the ports on EC2 at which your ignite cluster is runnin= g? >>>>>> >>>>>> On Fri, Aug 9, 2019 at 8:50 AM sri hari kali charan Tummala < >>>>>> kali.tummala@gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> thanks for replying I am following the below blog as per some exper= t >>>>>>> suggestion he asked me to use my laptop ip address and elastic ip a= ddress >>>>>>> of Ec2 instance ( >>>>>>> https://github.com/aws-samples/aws-big-data-blog/blob/9eb7cc30a2dfb= 02c15252a5bad03603a21451572/aws-blog-real-time-in-memory-oltp-and-analytics= -with-apache-ignite/src/main/java/com/amazon/dynamostreams/clientlibrary/St= reamsToIgnite.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.kasnacheev@gmail.com> wrote: >>>>>>> >>>>>>>> Hello! >>>>>>>> >>>>>>>> In my experience, on EC2 nodes usually use internal network to tal= k >>>>>>>> to each other. They will advertise these to any nodes trying to co= nnect, >>>>>>>> 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-coll= ocated >>>>>>>> clusters, and this includes thick client nodes. >>>>>>>> >>>>>>>> Regards, >>>>>>>> -- >>>>>>>> Ilya Kasnacheev >>>>>>>> >>>>>>>> >>>>>>>> =D0=BF=D1=82, 9 =D0=B0=D0=B2=D0=B3. 2019 =D0=B3. =D0=B2 03:35, sri= hari kali charan Tummala < >>>>>>>> kali.tummala@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 conn= ect 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 t= he remote >>>>>>>>> host I am able to access internet, ignite right now fails with be= low 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:4750= 3, >>>>>>>>> /52.204.222.254:47504, /52.204.222.254:47505, / >>>>>>>>> 52.204.222.254:47506, /52.204.222.254:47507, /52.204.222.254:4750= 8, >>>>>>>>> /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 ru= n in the >>>>>>>>> cluster by ssh to the box ? >>>>>>>>> >>>>>>>>> >>>>>>>>> https://aws.amazon.com/blogs/big-data/real-time-in-memory-oltp-an= d-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] >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Thanks & Regards >>>>>>>>> Sri Tummala >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks & Regards >>>>>>> Sri Tummala >>>>>>> >>>>>>> >>>>> >>>>> -- >>>>> Thanks & Regards >>>>> Sri Tummala >>>>> >>>>> >>> >>> -- >>> Thanks & Regards >>> Sri Tummala >>> >>> >> >> -- >> Thanks & Regards >> Sri Tummala >> >> > > -- > Thanks & Regards > Sri Tummala > > --00000000000083adb5058fb346d4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry for late response , your configuration looks correct= . I hope community ami will solve=C2=A0the problem.

-Him= anshu

On Fri, Aug 9, 2019 at 11:07 AM sri hari kali charan Tummala <= ;kali.tummala@gmail.com> w= rote:
the Blog has issue's the code which is in public s3 bucket doe= sn't exist so the ec2 instance doesn't have to ignite at all I rais= ed a concern with AWS Blog team, I will try community ami Ignite ec2 instan= ce or try to install ignite on my own manually.

On Fri, Aug 9, 2019 at 11:20= AM sri hari kali charan Tummala <kali.tummala@gmail.com> wrote:
please check.<= /div>
O= n Fri, Aug 9, 2019 at 10:58 AM sri hari kali charan Tummala <kali.tummala@gmail.com= > wrote:
give me couple of minutes I think I opened 0 to 65000 ports fo= r 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.iit@gmail.com&= gt; wrote:
Can you share screenshot of your inbound traffic setting, I thi= nk it need to be something like this

Example:=C2=A0

Inbound:=C2=A0
Custom TCP Rule TCP 10800 = - 10900 0.0.0.0/0 client= =C2=A0
Cust= om TCP Rule TCP 47500 - 47600 0.0.0.0/0 discovery=C2=A0
Custom TCP Rule TCP 47100 - 47200 0.0.0.0/0 communication=C2=A0

Outbound:=C2=A0
All traffic All All = 0.0.0.0/0=C2=A0
All traffic All All ::/0=C2=A0


On Fri, Aug 9, 2= 019 at 9:52 AM sri hari kali charan Tummala <kali.tummala@gmail.com> wrote:
<= /div>
yes= , all traffic inbound and outbound (TCP), I am able to do ssh also I am abl= e 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 <hima= nshu.iit@gmail.com> wrote:
Did you open the ports on EC2 at which y= our ignite cluster is running?

On Fri, Aug 9, 2019 at 8:50 AM sri hari kali = charan Tummala <kali.tummala@gmail.com> wrote:

Thanks
Sri=C2=A0




On= Fri, Aug 9, 2019 at 8:27 AM Ilya Kasnacheev <ilya.kasnacheev@gmail.com> wrot= e:
Hello!

In my experience, on EC2 nodes usu= ally 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 clus= ters, and this includes thick client nodes.

Regard= s,
--
Ilya Kasnacheev


<= div dir=3D"ltr" class=3D"gmail_attr">=D0=BF=D1=82, 9 =D0=B0=D0=B2=D0=B3. 20= 19 =D0=B3. =D0=B2 03:35, sri hari kali charan Tummala <kali.tummala@gmail.com>:<= br>
Hi All,=C2=A0

I am trying to connect a ignite ec2 instance (o= ne 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 fail= s with below error.

[20:14:54] Failed to connect to any address from= IP finder (will retry to join topology every 2000 ms; change 'reconnec= tDelay' to configure the frequency of retries): [/52.204.222.254:47500, /52.204.222.254:47501, /<= a href=3D"http://52.204.222.254:47502" target=3D"_blank">52.204.222.254:475= 02, /52.204.2= 22.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.25= 4:47510]

I am following below blog , can a= ny 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 ?


--
Thanks= & Regards
Sri Tummala



--
Thanks & Regards
Sri Tummala



--
Thanks & Regards
Sri Tummala



--
Thanks & Regards
Sri Tummala



--
Thanks & Regards<= div>Sri Tummala

--00000000000083adb5058fb346d4--