Redis Limits

Redis is an open source, key-value database built with an in-memory design that emphasizes speed. It has support for rich data types, atomic operations, and Lua scripting.


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 currently add DigitalOcean Cloud Firewalls to a database cluster’s trusted sources.

  • By default, database clusters only support up to 100 IP addresses as trusted sources. Different types of resources add varying numbers of IP addresses to your cluster. For example, Droplets typically have two IP addresses, one public and one private, both of which count towards the 100-address maximum. To add more than 100 IP addresses, contact support.

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

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

Redis Limits

  • DigitalOcean Managed Databases Redis 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
  • Redis database clusters do not support third-party clients to manage access control lists (ACLs).

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

  • Redis database clusters only support 1- and 2-node configurations, i.e. 1 primary node and up to 1 standby node. It does not support 3-node clustering, i.e. 2 standby nodes.

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

  • Redis 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 1GB (1024MB) of memory can have up to 10,000 simultaneous connections. A node with 4GB (4096MB) of memory can have up to 4 * 4096 = 16,384 simultaneous connections.

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

  • Migrations from AWS ElasticCache are not currently supported.

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

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.