Share via

Is there a way to riotx live replicate when the source database is Azure RedisEnterprise?

Dan Preece 20 Reputation points
2026-02-10T18:20:17.1+00:00

I'm trying to run riotx replicate --mode live from an Azure RedisEnterprise instance to an Azure Managed Redis instance and it gets this error:

10:36:52.744 [ThreadPoolTaskExecutor-2] INFO com.redis.spring.batch.item.redis.reader.KeyEventItemReader -- Creating queue with capacity 10,000

Listening ? % [= ] 0/? (0:00:00 / ?) ?/s

Scanning 0% [ ] 0/1910 (0:00:00 / ?) ?/s

10:36:53.170 [ThreadPoolTaskExecutor-2] INFO com.redis.spring.batch.item.redis.reader.KeyEventListenerContainer -- Retrieved config notify-keyspace-events:

10:36:53.171 [ThreadPoolTaskExecutor-2] ERROR org.springframework.batch.core.step.AbstractStep -- Encountered an error executing step liveStep in job replicate

Which I think is caused by AKE not being enabled in the notify-keyspace-events and therefore the tool isn't able to subscribe to key events to monitor changes. Is there a way to enable this for Azure RedisEnterprise or are we going to be restricted to just doing a replicate.

All of the data in our cache is just "cached" data like session state and other non-permanent data so we could just take the site down during our migration from the one cache to the other, but I was hoping that we could potentially use this tool to keep the site up while we migrate.

Azure Cache for Redis
Azure Cache for Redis

An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.

{count} votes

Answer accepted by question author
  1. Manoj Kumar Boyini 8,875 Reputation points Microsoft External Staff Moderator
    2026-02-10T19:35:44.1966667+00:00

    Hi Dan Preece,

    This behavior is expected. Azure Redis Enterprise does not support enabling the notify-keyspace-events configuration, which is required for RIOT‑X live replication (--mode live) to function. RIOT‑X depends on Redis keyspace notifications to subscribe to real‑time changes, but this capability is not available in Azure Redis Enterprise, and the setting cannot be modified at the service level.

    Because keyspace notifications cannot be enabled, RIOT‑X live migration is not supported from Azure Redis Enterprise. The only supported approach at this time is to use standard (offline) replication and perform the migration during a short maintenance window, which is what has chosen. If keyspace notification support is added to Azure Redis Enterprise in the future, RIOT‑X live replication would become possible, but this is not currently available.

    Hope this helps, Please let us know if you have any questions and concerns.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-02-10T18:20:25.0633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Currently, Azure Redis Enterprise does not support enabling the notify-keyspace-events configuration option, which is necessary for tools like RIOT-X to subscribe to key events for live replication. This limitation means that you will not be able to use the --mode live option with RIOT-X for replicating data from Azure Redis Enterprise to Azure Managed Redis.

    As a workaround, you can consider performing a standard data migration without live replication, especially since you mentioned that the data is non-permanent and can tolerate downtime during the migration process. This way, you can ensure that all data is migrated without the need for live synchronization.

    If your application can handle it, taking the site down during the migration might be the most straightforward approach given the current limitations.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.