Hi, well, this is what I meand with "script around".
I just thought it might have been a natural feature in Ignite. And maybe nodes may profit from being started in one JVM. But as I understand, this is not the case, there is no OOTB feature for this? Best wishes, Alexey On Fri, Jul 31, 2015 at 11:48 AM, Alexey Kuznetsov <[email protected]> wrote: > You could write a simple .sh file that will run ignite.sh in loop? > > On Fri, Jul 31, 2015 at 3:12 PM, Aleksei Valikov < > [email protected]> wrote: > >> Hi, >> >> is it possible to start several Ignite node at once? >> >> When I execute ./ignite.sh I'm getting just 1 node started. Assume I'm >> having a large machine with, say, 16 CPU Cores and I'd like to start 16 >> nodes. Is it possible via configuration? >> >> What would be even better, if I could start N-M (for instance 16-1=15) >> nodes, where N is the total number of CPU Cores available and M is a number >> of CPU Cores I'd like to reserve for management purposes. >> >> We're going to execute some third-party software which is (a) not >> intrinsically parallelizable (just uses 1 CPU Core) and (b) uses 100% CPU >> when it runs. So if we have a 16-Core machine, we'd like to be able to >> start this software 15 times (via 15 Ignite nodes) and resevre 1 CPU for >> management tasks like health checks, monitoring and so on. >> >> Is there a way to do it? Or should we just start ignite.sh 15 times and >> script around? >> >> Best wishes, >> Alexey >> > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
