OCI Cache Configurations
Manage the runtime properties of nodes and clusters in OCI Cache by configuring OCI Cache parameters.
OCI Cache configurations consist of specific parameter names and values that dictate how the engine processes on each node behaves at runtime. OCI Cache configurations are associated with particular versions of the related cache engine. Generally, newer engine versions include extra parameters to support enhanced functionalities. For information about Valkey and Redis cache engine-specific parameters, see Supported Configurations for OCI Cache.
OCI Cache Configurations Types
There are two types of OCI Cache configurations–default and custom. OCI Cache manages the default configurations and offers tailored settings for each major version of the Redis or Valkey engine. You can view and use the default configurations, but cannot modify them. You can instead create custom configurations for a particular cache engine version to customize the parameters.
- Custom configuration: Allows you to select a cache engine version and modify specific parameters. When creating or copying a configuration, you can edit the values of selected parameters. Once created, a configuration becomes immutable and can't be updated. To make changes, you would need to copy the configuration and modify it as necessary. A default configuration is the foundation for a custom configuration. Therefore, if a parameter value isn't specified, it inherits its value from the default or base configuration.
Custom configurations can be created or copied within a specific compartment.
- Default configuration: Consists of predefined Redis or Valkey parameters for a specific cache engine version. Default configurations can't be changed or deleted and serve as the base configuration when creating a custom configuration. Default configurations are listed under all compartments and are read-only resources owned and managed by OCI Cache. However, you can retrieve a list of default configurations by providing a compartment OCID, provided you have the
OCI_CACHE_CONFIGSET_INSPECT permission in that compartment.
To use OCI Cache configurations, you need appropriate IAM policies. See OCI Cache IAM Policies.
Associating Configurations with Clusters
You have the option to associate either a default or a custom configuration with your cluster; however, a custom configuration can be associated only after it has been created. For more information, see Creating an OCI Cache Configuration and Updating an OCI Cache Cluster's Cache Engine Configuration.
Retaining Configurations when Upgrading an OCI Cache Cluster's Cache Engine
You can upgrade clusters to newer versions of the Redis or Valkey cache engines. When upgrading, the configurations must be compatible with the newer engine version. You must select a compatible configuration while upgrading your cluster.
If your cluster is using a default configuration, you can choose a compatible default configuration. For custom configuration, you can create a copy and, while making the copy, select the appropriate cache engine version. For more information about any of the supported configurations, see Redis configuration file and Valkey configuration file.