well, Thanks for your advise. examples for yarn works. and I have figured it
out. It seems the ignite yarn deployment is not a good choice for windows.
The ignite source code override the onContainersAllocated function, and
when it tried ctx.setEnvironment(env) where env=System.getenv(); it caused
the problem.
In cmd, %=d:% has special meaning and can not be set.
Besides, the source code below can also cause errors:
ctx.setCommands(
Collections.singletonList(
(props.licencePath() != null ? "cp
gridgain-license.xml ./ignite/*/ || true && " : "")
+ "cp -r ./libs/* ./ignite/*/libs/ || true && "
+ "./ignite/*/bin/ignite.sh "
+ "./ignite-config.xml"
+ " -J-Xmx" + ((int)props.memoryPerNode()) + "m"
+ " -J-Xms" + ((int)props.memoryPerNode()) + "m"
+ IgniteYarnUtils.YARN_LOG_OUT
));
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/why-allocated-containers-much-more-than-INGNITE-NODE-COUNT-tp7226p7529.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
