There is another improvement to lazy loading of tenants; we need to cleanup local disk space taken by tenant who have become idle. The actual artifacts are stored in the repository which is fronted by the deployment synchronizer. We need a separate task to do this. This task can run once or twice a day & cleanup the disk space which had been taken by tenants who haven't been loaded in one or two days. If we don't do this, even if we have tenant & artifact lazy loading, we will eventually run out of disk space even if most of the tenants are idling.
-- *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
