Skip to main content
Version: Develop

Known Issues

This page describes concerns, limitations to be considered when allocating resources for the a9s Redis®* plans, and other known issues.

Known Issues​

  • Downtime during the migration. It will depend on the amount of data inside your Redis® Service Instance and network connection throughput between both Redis® Service Instances.
  • Every scenario in this migration was tested with Redis® instances following best practices for key naming. So, it is known that there may be problems when trying to migrate that when key names do not follow best practices. An example of this limitation is the use of keys with names containing binary content or other special characters can potentially cause issues during the migration. Please note that you might need to perform individual migration for any existing special keys, although we do provide an alternative Ruby-based solution in Migrate Redis® Using Manual DUMP & RESTORE for such cases.
  • If a Redis® Service Instance uses a logical database, in order to migrate the whole Redis® content, it is necessary to migrate the Redis® logical database one after another. A piece of information about logical databases:

    Out of the box, a Redis® instance supports 16 logical databases. These databases are effectively siloed off from one another, and when you run a command in one database, it doesn't affect any of the data stored in other databases in your Redis® instance.

Plan Upgrade Restrictions

Upgrades from single to cluster plans via the CF CLI update-service command are not possible for a9s Redis® 6 and above.

However, it is possible to migrate to a new (empty) instance matching the desired plan via the migration feature. This way the you are able to import your data from a single instance into a cluster instance. For more information please refer to our migration guide.

*Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by anynines GmbH is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and anynines GmbH.