Having done a bit more digging it seems the best option is to not set IGNITE_HOME at all but use IgniteConfiguration.setWorkDirectory(). I'm potentially going to be running multiple nodes on the same server and would prefer not to create individual start-up scripts for each (as I may want to add new nodes on the fly). Seems I could programmatically set the directory using the process id to guarantee I don't get a clash. Does this seem like a reasonable approach? Is there any way to do something similar for log files?
As a bit of extra information - I'm writing a server that uses a native library that is not thread safe, and due to native libraries being statically loaded can only have one instance per process. As I need to allow the server to process concurrent requests I will have many nodes running to process them but they will all (initially at least) be on the same physical server. Thanks Jon -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
