Valkey Limits

Managed Database Cluster Limits

• By default, you are limited to 10 clusters per account or team. If you reach this limit but need to create more database clusters, you can submit a request for a higher limit by clicking “Request Increase” on the window that shows when you attempt to create another cluster.

• You cannot resize cluster nodes to smaller sizes. To move from a bigger node to a smaller node, create a new cluster with the desired node size and import your data.

• You cannot delete the default database and user.

• Point-in-time-recovery (PITR) is limited to the last 7 days.

• VPC networks are only available to resources, accounts, and teams in the same region as the VPC network.

• You cannot migrate databases from clusters inside of DigitalOcean to other clusters inside of DigitalOcean using the online migration feature.

• You can only deploy standby nodes in the same region as your database cluster.

• You currently cannot add IPv6 rules to a database cluster’s trusted sources.

• When you restore from a backup, you must restore to a new node and re-add any read-only or standby nodes.

Valkey Limits

• DigitalOcean Managed Databases Valkey clusters do not support the following features:

  • Query statistics
  • Read-only nodes
  • Cluster forking
  • Connection pooling
  • Backups and point-in-time recovery (PITR)
  • Current and long-running queries

• Valkey database clusters do not support third-party clients to manage access control lists (ACLs).

• You cannot add users to Valkey database clusters using the DigitalOcean Control Panel.

• The amount of available memory in Valkey nodes is less than the total amount of RAM because some memory is reserved for the Valkey service to function normally. Learn more about Valkey memory usage.

• Valkey nodes can have up to either 10,000 simultaneous connections or 4 simultaneous connections per megabyte of memory, whichever is larger.

  For example, a node with 1GiB (1024MB) of memory can have up to 10,000 simultaneous connections. A node with 4GiB (4096MB) of memory can have up to 4 * 4096 = 16,384 simultaneous connections.

• You cannot create a standby node with the smallest node size (1GiB-RAM-1-vCPU).

• Migrations from AWS ElasticCache are not currently supported.

• On Valkey, each CPU in your cluster can handle up to 200 new connections per second. Any additional connection attempts within the second fail and users must try again. To work around this limitation, we recommend using connection pooling in your client.

• We do not currently support migrating managed database clusters on DigitalOcean to other managed database clusters on DigitalOcean using continuous migration. For example, you cannot migrate a managed database cluster from one DigitalOcean account to another. However, you can migrate with a dump.

• Valkey currently does not support the option to select a cluster’s storage size independently from its configuration plan.

Restricted Commands

For performance and security, you cannot use any of the following commands:

• bgrewriteaof: Starts a background append-only file rewrite
• cluster: Manages different Valkey cluster commands
• command: Provides more details about other Valkey commands
• debug: Contains sub-commands for debugging Valkey
• failover: Manages manual failover of a master to a replica
• migrate: Atomically transfers a key from a Valkey instance to another one
• role: Returns the role of the instance in the context of replication
• slaveof: Makes the server a replica of another instance, or promotes it as main/master
• acl: Manages Valkey Access Control Lists
• bgsave: Creates a snapshot of the dataset into a dump file
• config: Alters the configuration of a running Valkey server
• lastsave: Returns the UNIX timestamp of the last successful save to disk
• monitor: Streams back every command processed by the Valkey server
• replicaof: Makes the server a replica of another instance
• save: Synchronously saves the dataset to disk
• shutdown: Synchronously saves the dataset to disk and shuts down the server

The following eval commands are also restricted, but you can gain access to them by contacting support:

• eval: Executes a Lua script server-side
• eval_ro: Read-only variant of the eval command
• evalsha: Executes a script cached on the server side by its SHA1 digest
• evalsha_ro: Read-only variant of the evalsha command
• fcall: Calls a Valkey function
• fcall_ro: Read-only variant of the fcall command
• function: Manages Valkey functions
• script: Manages the script cache

Known Issues

Managed Database Cluster Known Issues

• You can’t use DigitalOcean’s Cloud Firewalls with managed databases. Until support is available, you can restrict access to nodes by their incoming IPv4 addresses.