CODEWITHSUNDEEP
azureredisazure-redis-cache
Malt
Malt

Reputation: 30335

Azure Redis Cache - how to correctly work against a replicated instance

According to this answer from an Azure Redis Cache team member, the Azure Redis Cache exposes a single endpoint. That endpoint is automatically routed to either the master or the slave node (on failover I assume). That answer also states that:

Azure... requires checks on the client side to ensure that the node is indeed Master or Slave

So clients see a single endpoint and have to sometime check which instance they're talking to - that raises some questions:

  1. When should a Redis client care whether it talks to the master or the slave node? Is it only to prevent inconsistency during failover, or are there other concerns here?

  2. How (and when) should a client check whether it's connected to the master or the slave instance? Is it by running info replication?

Upvotes: 1

Views: 1389

Answers (1)

evilSnobu
evilSnobu

Reputation: 26424

From the docs:

When the master node is rebooted, Azure Redis Cache fails over to the replica node and promotes it to master. During this failover, there may be a short interval in which connections may fail to the cache.

My understanding is you never connect to the slave because it is never exposed to you. If the master goes out, the slave is promoted to master and that's what you reconnect to.

Upvotes: 3

Related Questions