Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C1DAE200B29 for ; Wed, 15 Jun 2016 17:59:34 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C0B75160A63; Wed, 15 Jun 2016 15:59:34 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C3A99160A60 for ; Wed, 15 Jun 2016 17:59:33 +0200 (CEST) Received: (qmail 32166 invoked by uid 500); 15 Jun 2016 15:54:26 -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 29065 invoked by uid 99); 15 Jun 2016 15:47:54 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jun 2016 15:47:54 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 083E11A0D22 for ; Wed, 15 Jun 2016 15:35:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.18 X-Spam-Level: * X-Spam-Status: No, score=1.18 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YZLy7TwkxRSG for ; Wed, 15 Jun 2016 15:35:07 +0000 (UTC) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id EE3E25F4E5 for ; Wed, 15 Jun 2016 15:35:06 +0000 (UTC) Received: by mail-lf0-f41.google.com with SMTP id f6so17555216lfg.0 for ; Wed, 15 Jun 2016 08:35:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=7lbx7iZMD65/z1CPi2hv+tksJ3PjM17q6cpwfDe4DrE=; b=KwO8d2Mt4yShvwaRNVE/KrAckbV6J0cFgSNyJ43H89S3DortQ6eWZySaSKQ7VLLCb4 gxa3wyEWDx8NlYVzhK76sfXom30SrJrZlZlMwk9POH3kRDK1rbXy7cfSdockr/o4apL1 FgmsMy1RgymftsPP/s7tAFv5Pd9edzg+PZ7Fe1uyHg7uTXXprG2izZyvV30dmNvXdsFL s9L2hMCb1Zbdgk5Xlq2xtx2F5AQwSSFjVBapuTgSK7Oo2//m3wytB8RFTk/00lCtTHo4 uA47J+skjDlxr7/t1uDIzZVHY/Yv7dlGtPxyFUM6v8n9yqR977xXSsPnQSXbEwl5eidD 2RHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=7lbx7iZMD65/z1CPi2hv+tksJ3PjM17q6cpwfDe4DrE=; b=h4SQElPN42K9gaUsl6H4LQoeX7JoPWRpmdpAsQJC5ju8l9ZpF1rVRRVKWI7ZtIGOjg adl8ZmqD/uqvT/AMgdj+NhLcNEZvLhwT+Zza4FeHLRrmIhQslBEMJsM4cDB4eK/7ouXw Y3Ivg2be6bBJXqKDLukcvCZkXlj1ex+BIR5eZxxfgSXBIfV0q1wnXxT0GfpWZQ/ZKkl1 RHxZ4kUbJEi0BTCKACqlUMhNjljEIeQ9AHB33tYw3Hw4ScvvBlIQI5kNV4dAjAPTAWOh Dgagk2E+TFQZO2muj/J0eYH9rPg+gWXS0qIv1Jy2vvCx1fcRgijERNWojx9FSyj6StBg Z4SA== X-Gm-Message-State: ALyK8tIXtx45+mCMLOJf0ArDVOR6vcXhmJueaP5RmtISsK1xeXOci00ULIYTEUnbTrHbLjqi6FhUScV5g+wPDQ== X-Received: by 10.25.210.12 with SMTP id j12mr689810lfg.4.1466004906410; Wed, 15 Jun 2016 08:35:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.133.195 with HTTP; Wed, 15 Jun 2016 08:34:26 -0700 (PDT) In-Reply-To: References: From: Paolo Di Tommaso Date: Wed, 15 Jun 2016 17:34:26 +0200 Message-ID: Subject: Re: How deploy Ignite workers in a Spark cluster To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a11410c62af88c8053552dd81 archived-at: Wed, 15 Jun 2016 15:59:34 -0000 --001a11410c62af88c8053552dd81 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable OK, using `ic.close(false)` instead of `ic.close(true)` that exception is not reported. However I'm a bit confused. The close argument is named `shutdownIgniteOnWorkers` so I was thinking that is required to set it true to shutdown the Ignite daemon when the app is terminated. How it is supposed to be used that flag? Cheers, Paolo On Wed, Jun 15, 2016 at 5:06 PM, Paolo Di Tommaso wrote: > The version is 1.6.0#20160518-sha1:0b22c45b and the following is the > script I'm using. > > > https://github.com/pditommaso/gspark/blob/master/src/main/groovy/org/apac= he/ignite/examples/JavaIgniteSimpleApp.java > > > > Cheers, p > > > On Wed, Jun 15, 2016 at 5:00 PM, Alexei Scherbakov < > alexey.scherbakoff@gmail.com> wrote: > >> I don't think it's OK. >> >> Which Ingite's version do you use? >> >> 2016-06-15 15:35 GMT+03:00 Paolo Di Tommaso : >> >>> Great, now it works! Thanks a lot. >>> >>> >>> I have only a NPE during the application shutdown (you can find the >>> stack trace at this link ). Is this >>> normal? and in any case is there a way to avoid it? >>> >>> >>> Cheers, >>> Paolo >>> >>> >>> >>> On Wed, Jun 15, 2016 at 1:25 PM, Alexei Scherbakov < >>> alexey.scherbakoff@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> To automatically start Ignite nodes you must pass false parameter to >>>> 3-d IgniteContext argument like: >>>> >>>> // java >>>> SparcContext sc =3D ... >>>> new JavaIgniteContext<>(sc, new IgniteConfigProvider(), false);; >>>> >>>> or >>>> >>>> // scala >>>> SparcContext sc =3D ... >>>> new IgniteContext[String, String](sc,() =E2=87=92 configurationClo(), = false) >>>> >>>> 2016-06-15 13:31 GMT+03:00 Paolo Di Tommaso >>>> : >>>> >>>>> Hi all, >>>>> >>>>> I'm struggling deploying an Ignite application in a Spark (local) >>>>> cluster using the Embedded deploying described at this link >>>>> . >>>>> >>>>> >>>>> The documentation seems suggesting that Ignite workers are >>>>> automatically instantiated at runtime when submitting the Ignite app. >>>>> >>>>> Could you please confirm that this is the expected behaviour? >>>>> >>>>> >>>>> In my tests the when the application starts it simply hangs, reportin= g >>>>> this warning message: >>>>> >>>>> WARN org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Failed t= o >>>>> connect to any address from IP finder (will retry to join topology ev= ery 2 >>>>> secs): [/192.168.1.36:47500, /192.168.99.1:47500] >>>>> >>>>> It looks like there are not ignite daemons to which connect to. Also >>>>> inspecting the Spark worker log I'm unable to find any message produc= ed by >>>>> Ignite. I'm expecting instead to find the log messages produced by th= e >>>>> ignite daemon startup. >>>>> >>>>> >>>>> Any idea what's wrong? >>>>> >>>>> >>>>> Cheers, >>>>> Paolo >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Best regards, >>>> Alexei Scherbakov >>>> >>> >>> >> >> >> -- >> >> Best regards, >> Alexei Scherbakov >> > > --001a11410c62af88c8053552dd81 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
OK, using `ic.close(false)` instead of `ic.close(true)` th= at exception is not reported.=C2=A0

However I'm a bi= t confused. The close argument is named `shutdownIgniteOnWorkers` so I was = thinking that is required to set it true to shutdown the Ignite daemon when= the app is terminated.=C2=A0

How it is supposed t= o be used that flag?=C2=A0


Cheers,
P= aolo


On Wed, Jun 15, 2016 at 5:06 PM, Paolo Di Tommaso <paolo.ditommaso@gmail.com> wrote:
The version is 1.6.0#20160518-sha1:0b22c45b and th= e following is the script I'm using.=C2=A0



=

Cheers, p


On Wed, Jun 15, 2016 at 5:00 PM, Alexei Scherbakov &l= t;alexey.= scherbakoff@gmail.com> wrote:
I don't think it's OK.

Which Ingite's version do you use?

2016-06-15 15:35 GMT+03:00 Paolo Di T= ommaso <paolo.ditommaso@gmail.com>:
Great, now it works! Thanks a lot.=C2=A0=


I have only a NPE during the application= shutdown (you can find the stack trace=C2=A0at this link). Is this normal? and in any = case is there a way to avoid it?=C2=A0


<= div>Cheers,
Paolo


<= div>

On Wed, Jun 1= 5, 2016 at 1:25 PM, Alexei Scherbakov <alexey.scherbakoff@gmail= .com> wrote:
Hi,

To automatically start Ignite nodes you must pass= false parameter to 3-d IgniteContext argument like:

// java
SparcContext sc =3D ...
new JavaIgniteContex= t<>(sc, new IgniteConfigProvider(), false);;

or

// scala
SparcContext sc =3D ...
=
new IgniteContext[String, String](sc,() =E2=87=92 configurationClo(),= false)

2016-06-15 13:31 GMT+03:00 Paolo Di Tommaso <paolo.ditommaso= @gmail.com>:
Hi all,=C2=A0

I'm struggling deploying an Ignite = application in a Spark (local) cluster using the Embedded deploying describ= ed at this link. =C2=A0

The documentation seems suggesting that Ignite workers are = automatically instantiated at runtime when submitting the Ignite app.
=

Could you please confirm that this is the expected beha= viour?=C2=A0


In my tests the when t= he application starts it simply hangs, reporting this warning message:=C2= =A0

WARN =C2=A0org.apache.ignite.spi.discovery= .tcp.TcpDiscoverySpi =C2=A0- Failed to connect to any address from IP finde= r (will retry to join topology every 2 secs): [/192.168.1.36:47500, /192.168.99.1:47500]
=

It looks like there are not ignite daemons to which con= nect to. Also inspecting the Spark worker log I'm unable to find any me= ssage produced by Ignite. I'm expecting instead to find the log message= s produced by the ignite daemon startup.=C2=A0

Any idea what's wrong?=C2=A0


<= /div>
Cheers,
Paolo




<= font color=3D"#888888">--

Best regards,
Alexei Scherbakov
=




--
=

Best regards,
Alexei Scherbakov


--001a11410c62af88c8053552dd81--