Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indicate to Global Caches how long a resource should be cached for #43

Open
6a6d74 opened this issue Oct 16, 2023 · 1 comment
Open

Comments

@6a6d74
Copy link
Collaborator

6a6d74 commented Oct 16, 2023

As discussed at ET-W2AT meeting, 16-Oct-2023.

WIS2 Manual (Tech Regs) states:

"""
4.5.4 Based on received notifications, a Global Cache shall download core data from WIS nodes or other Global Caches and store for a duration compatible with the real-time or near real-time schedule of the data and not less than 24-hours.
"""

The default period for caching resources is 24-hours. But some (near) real time might need to be kept for longer based on the "real-time or near real-time schedule". Its a WMO Programme decision about how long data should be cached for, agreed with the WIS2 operators - in a process that's yet to be defined.

A mechanism is required to inform Global Caches to cache content for a duration other than 24-hours - usually longer, but perhaps shorter too.

It seems likely that this would be a per-object policy, i.e., each object that is cached should indicate the length of time it should be cached. The simplest way to do this would be to add a cache-duration attribute to the notification message.

A Global Cache may ignore the cache-duration statement, for example, if the duration was set to an excessively long period that compromised the ability of the Global Cache to perform. In "tech regs speak": the Global Cache should respect the cache-duration value.

@amilan17
Copy link
Member

note: current guide differs from text above content. https://wmo-im.github.io/wis2-guide/guide/wis2-guide-DRAFT.html#_2_4_3_global_cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: For end of Pre-operational phase (Dec 2024)
Development

No branches or pull requests

2 participants