CachePolicy is a datatype for a policy for choosing which segments to cache on local disk when overcommiting local storage with bucket storage.

This can be used to protect certain repositories for local storage, such that searching other repositories does not evict them.

A cache policy in LogScale divides segments into prioritized and non-prioritized. When segments needs to be evicted from local storage, try evicting non-prioritized segments before prioritized ones.

A cache policy can be set either on one of three levels, in order of precedence: Repo, Org, Globally.

When determining the cache policy for a repo LogScale first checks if there is a cache policy set on the repository. If none is set, LogScale checks the organization. If none is set there, the global setting is checked.

Table: CachePolicy

ParameterTypeRequiredDefaultDescription
Some arguments may be required, as indicated in the Required column. For some fields, this column indicates that a result will always be returned for this column.
Table last updated: Sep 24, 2024
prioritizeMillislong  Prioritize caching newer segments.