You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In December @golfvert (Remy) and I noticed that the Global Caches did not seem to be caching much of the data published by GTS-to-WIS2 Gateways. See the image below showing:
number of messages published by "origin" (one of the GTS-to-WIS2 gateways)
number of messages "missed" by the UK-USA Global Cache (i.e., those messages that have not been published by the GC after 10-minutes and are considered to be not cached).
One issue from DWD's gateway was that the download links in the WNMs weren't resolving, giving the following error:
4XX Not found or no permission
Kai fixed this problem.
Now that WIS2 is operational, we need to determine if this behaviour is still persisting.
(BTW - ignore the Gateway flatlining 3/4 of the way through - that was an offline period)
The text was updated successfully, but these errors were encountered:
6a6d74
changed the title
Global Caches not caching a significant proportion of data published by GTS-to-WOS2 gateways
Global Caches not caching a significant proportion of data published by GTS-to-WIS2 gateways
Jan 7, 2025
Talking with @golfvert offline, I can confirm that the data excludesrecommended data that the Global Caches ignore.
Note that core data with notification messages that state properties.cache=false (i.e., instructing the GC not to cache the data object) should still result in the GC publishing a new notification message - albeit with a URL pointing back to the original source.
In December @golfvert (Remy) and I noticed that the Global Caches did not seem to be caching much of the data published by GTS-to-WIS2 Gateways. See the image below showing:
One issue from DWD's gateway was that the download links in the WNMs weren't resolving, giving the following error:
4XX Not found or no permission
Kai fixed this problem.
Now that WIS2 is operational, we need to determine if this behaviour is still persisting.
(BTW - ignore the Gateway flatlining 3/4 of the way through - that was an offline period)
The text was updated successfully, but these errors were encountered: