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
hi,
Thanks for your advise. I found that launch container always failed. because
there is a syntax error in launcontainer.cmd. In launchcontainer.cmd, there
are some lines with syntax error:
@set IGNITE_RELEASES_DIR=/ignite/releases/
@if %errorlevel% neq 0 exit /b %errorlevel%
@set
well, I tried to integrate ignite with yarn and set IGNITE_NODE_COUNT equals
2, but when running the ignite yarn application, I found the total allocated
containers is 156 and kept increasing. I'm really confused, what is the
relationship between ignite node and allocated containers?
--
View
Well, I am testing the read and write performance between ignite and redis. I
found that redis has a pipelined method that improve performance a lot. Is
there anything like redis pipelined in ignite?? I tried async but the
performance didn't change, maybe there is something wrong? would you
