That's quite strange. I've just tested same scenario and works fine for me. If you do any change on user, the user is invalidated from cache on node-1 and this change about invalidation should be propagated to node-2 . As long as you have shared database, node-2 should then retrieve newest data about shared user from database.

I would suggest to try this:

* Make sure that your infinispan cluster is correctly set. You can check it by seeing the message similar to this in server.log of both nodes: node_1 | 10:49:50,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-10,shared=udp) ISPN000094: Received new cluster view: [node1/keycloak|1] (2) [node1/keycloak, node2/keycloak]

* Make sure that you enable "infinispan" as provider of realmCache and userCache and configured connectionsInfinispan . When you open admin console on any node like: http://node-1:8080/auth/admin/master/console/index.html#/server-info

you should see:
connectionsInfinispan default
realmCache infinispan
userCache infinispan
userSessions infinispan

* If still seeing issues, you can try to enable trace logging for "org.keycloak.models.cache.infinispan" category.

Hope this helps,
Marek

On 17.1.2015 04:32, prab rrrr wrote:

Anyone noticed any issues with Infinispan? I saw a weird issue. After setting up a cluster with two nodes, made some changes on node-1 (created a user and changed the first name). While the user appeared on node-2, the change to the first name didn't make it. Restarting the node-2 didn't help either. Wondering if Infinispan is preventing all the changes to be picked up from database. If so, what settings would ensure that the data is consistent between the nodes?

Thanks,

Raghu
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user