Hi, To automatically start Ignite nodes you must pass false parameter to 3-d IgniteContext argument like:
// java SparcContext sc = ... new JavaIgniteContext<>(sc, new IgniteConfigProvider(), false);; or // scala SparcContext sc = ... new IgniteContext[String, String](sc,() ⇒ configurationClo(), false) 2016-06-15 13:31 GMT+03:00 Paolo Di Tommaso <[email protected]>: > Hi all, > > I'm struggling deploying an Ignite application in a Spark (local) cluster > using the Embedded deploying described at this link > <https://apacheignite-fs.readme.io/docs/installation-deployment#embedded-deployment>. > > > 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, reporting > this warning message: > > WARN org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi - Failed to > connect to any address from IP finder (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 connect to. Also > inspecting the Spark worker log I'm unable to find any message produced by > Ignite. I'm expecting instead to find the log messages produced by the > ignite daemon startup. > > > Any idea what's wrong? > > > Cheers, > Paolo > > -- Best regards, Alexei Scherbakov
