Heap memory is managed by JMV, not by application, so there is no way to allocate it on per-node basis. But you can use off-heap memory instead - it's fully managed by Ignite and you're allowed to limit the amount of memory used for particular cache. Please refer to this documentation page for more information and configuration examples: https://apacheignite.readme.io/docs/off-heap-memory
As for CPUs, I still don't see why do you need this. These CPUs are not "allocated" by an Ignite node, they are just available to it. So if there is enough CPU time for both Ignite and your application which share one box, it will work. In other words, let operating system properly manage the resources. Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Setting-the-number-of-cores-and-heap-size-on-a-node-tp831p852.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
