----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, 15 September, 2014 2:41:39 PM
Subject: Re: [keycloak-dev] Clustering and user sessions
Only works for session refreshes. Also leaves an open window that the
user is still logged in after they log out.
Yes, it's only for session refreshes, but IMO that's going to be the biggest
traffic generator. For login and logouts we're going to have to send a message per
event.
On 9/15/2014 8:28 AM, Stian Thorgersen wrote:
> Had an idea with regards to clustering and user sessions. Instead of
> sending messages to the cluster when a individual user session is
> refreshed all nodes send a periodic update message. Obviously that's only
> for user sessions and not for admin updates, where we should still send
> invalidation messages for each update.
>
> Each node would keep a note of all user sessions where it has updated
> LastSessionRefresh, and once every period it would send this list to all
> nodes. This should mean that instead of sending a message every time a
> single session is updated, we send a single message per node every 60
> seconds or so (should be configurable). When receiving a message from the
> cluster the node would go through the list and update the user sessions
> where the received LastSessionRefresh is higher than the one it has
> itself. Nodes still use the mem user sessions store, but with the cache on
> top.
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev