Caches that span across entire deployments containing multiple sub-systems(clusters) don't scale. We have discussed this several times in the past. The solution was to have a notification mechanism where one or a few nodes in a cluster will receive notifications when changes in one sub-system (e.g. publisher), should affect other sub-systems. These representative nodes can then take care of reloading/expiring their sub-system specific caches.
Azeez On Fri, Sep 20, 2013 at 2:06 AM, Darshana Gunawardana <[email protected]>wrote: > Adding dev@ > > > > On Fri, Sep 20, 2013 at 2:04 AM, Darshana Gunawardana > <[email protected]>wrote: > >> Hi all, >> >> I have worked on some recent issues on APIM which thought to be caching >> issues in permissions. When i try to isolate the issue, i suspects that >> this is more general problem of the usage of caching in APIM distributed >> deployment. >> >> "To work distributed caching, nodes (which intended to share caches) >> needed to be in same cluster." >> >> Based on above fact, the problem is how it gonna facilitate APIM >> distributed setup where store/publisher needed to sync information about >> API resources. >> >> For an example if we add a new API on publisher it not gonna display on >> store, if the store already has cached information on APIs and publisher >> has no way to tell to store the cache is out-dated. Here simple registry >> caching on store and publisher cause the issue and there can be many >> several scenarios like this. >> >> The above scenario works as expected on following cases, >> - Waiting for a 15 mins which is caching timeout >> - Restarting the server >> - Adding store & publisher to a same cluster. >> >> Maybe i'm missing some obvious thing here? If so please sorted me out. If >> not how does in earlier versions manage this? I believe this not a >> Hazelcast specific scenario. >> >> Thanks >> >> -- >> Regards, >> >> * >> Darshana Gunawardana >> *Software Engineer >> WSO2 Inc.; http://wso2.com* >> E-mail: [email protected] >> **Mobile: +94718566859 >> *Lean . Enterprise . Middleware >> > > > > -- > Regards, > > * > Darshana Gunawardana > *Software Engineer > WSO2 Inc.; http://wso2.com* > E-mail: [email protected] > **Mobile: +94718566859 > *Lean . Enterprise . Middleware > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
