@@ -72,49 +72,41 @@ <h1 style="text-align:center;">ERDDAP Changes</h1>
7272
7373
7474< h2 > < a class ="selfLink " id ="changes2.20 " href ="#changes2.20 " rel ="bookmark "> Changes</ a >
75- in ERDDAP version 2.20 (released 2022-09-30 )</ h2 >
75+ in ERDDAP version 2.21 (released 2022-10-09 )</ h2 >
7676< ul >
7777< li > < strong > New Features and Changes (for users):</ strong >
7878 < ul >
7979 < li > (None)
8080 < br >
8181 </ ul >
8282< li > < strong > Things ERDDAP Administrators Need to Know and Do:</ strong >
83- < ul >
84- < li > TO DO: In [tomcat]/conf/context.xml, right before < kbd > </Context></ kbd > ,
85- change the < kbd > Resources</ kbd > tag (or add it if it isn't already there) to
86- increase the < kbd > cacheMaxSize</ kbd > setting from 80000 (or whatever it was) to 200000:
87- < br > < kbd > <Resources cachingAllowed="true" cacheMaxSize="200000" /></ kbd >
88- < br > This avoids numerous warnings in catalina.out that all start with
89- < br > < kbd > "WARNING [main] org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/WEB-INF/classes/..."</ kbd >
83+ < ul >
84+ < li > BUG FIX: Sometimes, the new email system attempted to log in too often,
85+ which caused Google Email servers to reject all future log in attempts. Now,
86+ the email system avoids this and related problems.
9087 < br >
91-
88+ </ ul >
89+ </ ul >
90+
91+ <!-- ****************************************************************************** -->
92+
93+
94+ < h2 > < a class ="selfLink " id ="changes2.20 " href ="#changes2.20 " rel ="bookmark "> Changes</ a >
95+ in ERDDAP version 2.20 (released 2022-09-30)</ h2 >
96+ < ul >
97+ < li > < strong > New Features and Changes (for users):</ strong >
98+ < ul >
99+ < li > (None)
100+ < br >
101+ </ ul >
102+ < li > < strong > Things ERDDAP Administrators Need to Know and Do:</ strong >
103+ < ul >
92104 < li > IMPROVED: We re-enabled the old memory management system (Math2.ensureMemoryAvailable) and modified
93105 the new memory management system (EDStatic.shedThisRequest) to work better with it.
94- < p > ERDDAP shouldn't ever crash or freeze up. If it does, one of the
95- most likely causes is insufficient memory. You can monitor memory usage
96- by looking at the status.html web page, which now includes a line like
97- < br > < kbd > 0 gc calls, 0 requests shed, and 0 dangerousMemoryEmails since last major LoadDatasets</ kbd >
98- < br > (those are progressively more serious events)
99- < br > and a < kbd > gc Calls</ kbd > column in the table of statistics.
100- You can tell how memory-stressed your ERDDAP is by watching these numbers
101- in addition to the < kbd > MB inUse</ kbd > columns.
102- Higher numbers indicate more stress.
103- < ul >
104- < li > < kbd > MB inUse</ kbd > should always be less than half of your Xmx memory setting.
105- Larger numbers are serious trouble.
106- < li > < kbd > gc calls</ kbd > indicates the number of times ERDDAP called the
107- garbage collector to try to alleviate high memory usage.
108- < li > < kbd > shed</ kbd > indicates the number of incoming requests that
109- were shed (with HTTP error number 503, Service Unavailable) because
110- memory use was already too high. Ideally, no requests should be shed.
111- < li > < kbd > dangerousMemoryEmails</ kbd > -
112- If memory use becomes dangerously high, ERDDAP sends an email to the email addresses listed in
113- emailEverythingToCSV (in setup.xml) with a list of the active user requests. As the email says,
114- please forward these emails to erd.data at noaa.gov so we can use the information
115- to improve future versions of ERDDAP.
106+ See < a rel ="help "
107+ href ="https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#MemoryStatus "
108+ > Memory Status</ a > for details.
116109 < br >
117- </ ul >
118110
119111 < li > CHANGED: The default for <ipAddressMaxRequests> in datasets.xml
120112 was increased from 7 to 15. It's clear that some legitimate WMS clients
@@ -159,6 +151,12 @@ <h2><a class="selfLink" id="changes2.19" href="#changes2.19" rel="bookmark">Chan
159151 There are no other changes that you need to make to your ERDDAP
160152 installation related to this change. In other words, ERDDAP works
161153 as it did before.
154+
155+ < p > Don't forget to make the ERDDAP-related changes to Tomcat's server.xml and context.xml
156+ when you upgrade Tomcat. See ERDDAP's
157+ < a rel ="help " href ="https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#tomcat "
158+ > Tomcat installation instructions</ a > .
159+
162160 < p > My impression of Java 17 is that it prefers more processing power and memory
163161 for long-running, larger applications like ERDDAP, so it works slightly slower
164162 than Java 8 with low power computers (e.g., 2 cores and minimal RAM)
@@ -168,10 +166,10 @@ <h2><a class="selfLink" id="changes2.19" href="#changes2.19" rel="bookmark">Chan
168166 < a rel ="bookmark " href ="https://www.howtogeek.com/668986/how-to-use-the-linux-top-command-and-understand-its-output/ "> top< img
169167 src ="../images/external.png " alt =" (external link) "
170168 title ="This link to an external website does not constitute an endorsement. "> </ a >
171- to check resource usage and consider giving ERDDAP more resources.
169+ to check resource usage and consider giving ERDDAP more resources, notably more memory .
172170 Memory is cheap! Most phones have more processors and memory than
173171 the servers that some of you are using to run ERDDAP!
174- Thanks to Erin Turnbull.
172+ < br > Thanks to Erin Turnbull.
175173 < br >
176174 < li > TO DO: If you use ERDDAP to access Cassandra, for Cassandra, you need to keep using the version
177175 of Java that you were using for running the Cassandra.
@@ -181,6 +179,7 @@ <h2><a class="selfLink" id="changes2.19" href="#changes2.19" rel="bookmark">Chan
181179 consider changing to these settings in your datasets.xml file:< kbd >
182180 < br > <nGridThreads>3</nGridThreads>
183181 < br > <nTableThreads>3</nTableThreads> </ kbd >
182+ < br > If your server has fewer resources, stick to "1" for both of those settings.
184183 < br > The nThreads systems for EDDGridFromFiles and EDDTableFromFiles were significantly improved.
185184 These changes led to a huge speed improvement (e.g., 2X speedup when nThreads is set to 2 or more)
186185 for the most challenging requests (when a large number of files must be processed to gather the results).
@@ -6953,7 +6952,7 @@ <h2><a class="selfLink" id="contact" href="#contact" rel="bookmark">Contact</a><
69536952
69546953< br >
69556954< hr >
6956- < p > ERDDAP, Version 2.20
6955+ < p > ERDDAP, Version 2.21
69576956< br > < a href ="https://coastwatch.pfeg.noaa.gov/erddap/legal.html "> Disclaimers</ a > |
69586957 < a href ="https://coastwatch.pfeg.noaa.gov/erddap/legal.html#privacyPolicy "> Privacy Policy</ a >
69596958
0 commit comments