Evgenii,
"Client node didn't even join the topology. Most possible you have incorrect
discovery configuration. Also, I'd recommend to check client logs for more
information why node can't connect to the cluster."
In Zeppelin setup for the Ignite interpreter, it uses the same configuration
for Scala connection as it does for Ignite SQL connections. I have tested
the SQL connections, and they work perfectly (both the 11211 port and the
Node Client using XML). It is odd that the Scala connection doesn't work.
As far as client logs are concerned, Zeppelin only generates the interpreter
logs, such as, zeppelin-interpreter-ignite--zeppelin-db54cc4b4-kppw2.log,
and that log only states that the job was started:
INFO [2018-11-03 09:15:41,893] ({pool-2-thread-5}
SchedulerFactory.java[jobStarted]:109) - Job 20181102-071721_1550658378
started by scheduler org.apache.zeppelin.ignite.IgniteInterpreter113609227
And then nothing after that, as the interpreter process hangs.
Do you have any idea how to turn on DEBUG level logging for the Zeppelin
Ignite interpreter?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
