<div dir="ltr">One main issue with testing the cluster is identifying when something is loaded from cache instead of db.</div><div class="gmail_extra"><br><div class="gmail_quote">On 3 December 2015 at 14:22, Marko Strukelj <span dir="ltr"><<a href="mailto:mstrukel@redhat.com" target="_blank">mstrukel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 for testing the clustering, but it will take some time to develop that unless someone already started on it. <div><br></div><div>Maybe by using Arquillian Cube in combination with keycloak-ha-postgres ...</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Dec 3, 2015 at 1:50 PM, Stian Thorgersen <span dir="ltr"><<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">There's still some outstanding issues with the realm cache. It works, but can and should be improved for 1.8.<div><br></div><div>One issue was that once the realm is updated any methods on clients, roles or groups returns the underlying adapter instead of the cache adapters. As a work around in 1.7 it now ejects all clients for a realm when it sees any changes.</div><div><br></div><div>We have a few potential ways to solve this:</div><div><br></div><div>a) try to always return cache adapters - I went down this road attacking it from a few different approaches, but was never successful as there was always something that didn't work</div><div>b) only cache realms and have everything else hang off it - this is my preferred option for now. As long as updating clients requires invalidating the realm it seems a bit over the top to have separate caches for everything</div><div>c) make the cache smarter - instead of invalidating a realm, make sure we add/remove the clients, etc..</div><div><br></div><div>We also need more automated testing around clustering. Late in 1.7 release process I identified that caches where invalidated when other nodes loaded things to it, so effectively the cache wasn't working at all in a cluster.</div><div><br></div><div>Thoughts?</div></div>
<br></div></div>_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></blockquote></div><br></div>
</blockquote></div><br></div>