Hi, The code there is not completely correct and there is a ticket for that [1]. Essentially, if there is some kind of misconfiguration, the corresponding exception will be lost and the one you got will be thrown. Most likely that's what happening in your test.
I would recommend to execute a Spark closure which will simply call Ignition.start() with your configuration. If my assumption is right, you will see the exception that causes the issue. Let me know if it helps. [1] https://issues.apache.org/jira/browse/IGNITE-2942 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Should-Ignition-start-method-to-be-called-in-a-spark-igniteRDD-app-tp3854p3870.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
