[Building Sakai] User pre-caching and clustering

Aaron Zeckoski azeckoski at unicon.net
Thu May 8 21:21:49 PDT 2014


Joshua,
The time it takes is dependent on how fast your LDAP is, how good the
connection is, and various other factors, but since Sakai 2.9 has no
distributed caching you would have to load that on every server. It
might be possible to distribute that cache in Sakai 10 by taking
advantage of some of the work I and others at Unicon did to support
distributed caching in Sakai. Unfortunately, certain object classes
(like User) cannot be distributed without extra code work (they have
to be made completely Serializable) so it would not be trivial but it
is at least possible.

Aside from switching to a distributed cache, you probably would have
to find a way to create a faster intermediate source of the data which
is not the LDAP (but gets the data from the LDAP) and write a provider
to go against that source instead of LDAP. I don't think that is a
very good solution though.
-AZ


On Thu, May 8, 2014 at 8:56 PM, Joshua Swink <joshua.swink at gmail.com> wrote:
> I'm looking into the user pre-caching feature, and it appears that the daily
> refresh would need to run on every node in a cluster.
>
> https://jira.sakaiproject.org/browse/KNL-826
>
> Is that the case? Does anyone have suggestions for running it on one node so
> that the entire cluster has the info? I ask because it looks to be taking
> about an hour to run.
>
> Josh
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"



-- 
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile


More information about the sakai-dev mailing list