Knock on wood: no additional Hazelcast errors after increasing the
heartbeat timeout to something more than the heartbeat interval. ;-)
Tom.
On 06/02/2016 09:33 AM, Travis Schmidt wrote:
> Looked a little further into this. The Hazelcast documentation says the
> heartbeat interval is 1 second, looking into the Hazelcast code we see
> that it is actually defaulted to 5 seconds.
>
> HEARTBEAT_INTERVAL_SECONDS("hazelcast.heartbeat.interval.seconds", 5,
> SECONDS),
>
> So the default configuration in CAS basically set this up to be a race
> condition to determine if a node is dead or alive.
>
> On Thu, Jun 2, 2016 at 9:29 AM Misagh Moayyed <[email protected]
> <mailto:[email protected]>> wrote:
>
> Probably too aggressive of a default, yes, but the UM is in seconds:
>
> # hz.cluster.max.heartbeat.seconds=5
>
> Enable that property and set it to 300.
--
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/5751EE2E.1030808%40ucdavis.edu.
For more options, visit https://groups.google.com/a/apereo.org/d/optout.
