Hi Aswin, As you are using one JVM per box, enabling\disabling sharedMemory should not have effect as it shouldn't be used by Ignite. AFAIK, shared memory can cause problems in some cases.
Why do you need port range >0 if each of Ignite instances have unique IP? Ignite can scan all discovery port range to find other nodes. On Wed, Mar 1, 2017 at 1:00 AM, atricuix <aswi...@gmail.com> wrote: > Hi Andrey, > > Thanks for looking into this. > > A bit confused. We use only one JVM per box and each ignite server JVM has > a > different IP address. > So by default localPort() also uses 100 ports starting 47100 / 47500. We > have already opened the entire range in our ingress security rules. > > I did not understand the sharedMemory part. Are you suggesting to disable > it > as we use a VM? > > Thanks, > Aswin > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Failure-to-start-a-bigger-ignite- > cluster-tp10852p10959.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Andrey V. Mashenkov
