PUT /v2/databases/{database_cluster_uuid}/eviction_policy

To configure an eviction policy for an existing Redis or Valkey cluster, send a PUT request to /v2/databases/$DATABASE_ID/eviction_policy specifying the desired policy.

Servers

Path parameters

Name Type Required Description
database_cluster_uuid String Yes

A unique identifier for a database cluster.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
eviction_policy String Yes

A string specifying the desired eviction policy for a Redis or Valkey cluster.

  • noeviction: Don't evict any data, returns error when memory limit is reached.
  • allkeys_lru: Evict any key, least recently used (LRU) first.
  • allkeys_random: Evict keys in a random order.
  • volatile_lru: Evict keys with expiration only, least recently used (LRU) first.
  • volatile_random: Evict keys with expiration only in a random order.
  • volatile_ttl: Evict keys with expiration only, shortest time-to-live (TTL) first.

Possible values:

  • "noeviction"
  • "allkeys_random"
  • "volatile_lru"
  • "allkeys_lru"
  • "volatile_random"
  • "volatile_ttl"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.