clustering with HazelcastStorageService

[Paul B. Henson]

> From: Kevin Foote
> Sent: Wednesday, April 27, 2016 5:01 PM
>
> Once JJ tracked down our original issue [1] the session storage has not had
> errors.

Yes, I saw that issue; thanks for working out the kinks before I got around to deploying :).

> Moving to production the first thing I noticed was the container needed
> more memory I have it set at 2g currently and

I was planning to err on the side of caution; my production deployment will consist of a physical box with 8G and I was going to allocate 4G each to the two virtual machines that will accompany it.

> single node. I believe I need to adjust the TCP
> connection parameters a bit, possibly heartbeat if that is possible.

One of the sample parameters on the unicon github page is hazelcast.max.no.heartbeat.seconds, is that the one you're thinking of? I'm pretty sure you should be able to configure any available parameter. I never had to tweak any of the underlying cluster parameters on my CAS deployment, it's been pretty rock solid.

Thanks for the info…