NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Kyle:I think this is a problem for large installations; the TDS has to read through the "static catalogs" at startup to find all of the data roots.
We have tried to minimize the use of static catalogs by using dynamically generated catalogs (datasetScan), which generates them on the fly. Aggregations can also be dynamic by using the scan element.
I wonder if these are possible solutions for you? If not, can you characterize what you are doing, so we can understand what you need? We are looking at ways to make the "large number of static catalogs" use case more efficient, but havent started working on it yet.
For your specific question, obviously the issue is the object caching inside the TDS, and since restarting the TDS clears everything, that works. However thats a pretty big price to pay. Reinit should work, but probably you have found a bug. I probably have to recreate it here to understand more details. But even reinit is really too blunt.
Anyway, can you describe how often and what changes, and send a sample catalog?
thanks, John On 2/18/2011 11:35 AM, Kyle Wilcox wrote:
Hi all - I'm looking for some best practices for reloading the THREDDS catalog. How do large TDS implementation deal with a changing catalog? Do you reload the entire THREDDS application to pick up changes? Are there just not that many catalog changes, so a restart is not a big deal? Does the THREDDS application always need to be reloaded in some way if the catalog is updated? I'm trying to get away from having to reload large aggregations every time the catalog is changed. For example: When change an attribute value via NcML, the OPeNDAP form does not update with the changes automatically. * Using the "Reinitialize" link on the admin panel DOES NOT refresh the form (even after clearing browser cache) * Using the links on the admin panel to clear various caches DOES NOT refresh the form. * Using the "Disable Caches" link on the admin panel and then clicking "Reinitialize" DOES refresh the dataset. Something tells me this is not what I should be doing. * Restarting Tomcat DOES reset the dataset * Using 'touch $CATALINA_HOME/webapps/thredds/WEB-INF/web.xml' DOES refresh the dataset. This is the same as using the "Reload" link on the Tomcat Manager. --------- Kyle Wilcox, Engineer Applied Science Associates 55 Village Square Drive South Kingstown, RI 02879 p: (401) 789-6224 e: kwilcox@xxxxxxxxxxxxxx _______________________________________________ thredds mailing list thredds@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
thredds archives: