Ssekidde  Nat

Ssekidde Nat

1624883340

Zone Redundancy for Azure Cache for Redis now in preview

Between waves of pandemics, hurricanes, and wildfires, you don’t need cloud infrastructure adding to your list of worries this year. Fortunately, there has never been a better time to ensure your Azure deployments stay resilient. Availability zones are one of the best ways to mitigate risks from outages and disasters. With that in mind, we are announcing the preview for zone redundancy in Azure Cache for Redis.

Availability Zones on Azure

Azure Availability Zones are geographically isolated datacenter locations within an Azure region, providing redundant power, cooling, and networking. By maintaining a physically separate set of resources with the low latency from remaining in the same region, Azure Availability Zones provide a high availability solution that is crucial for businesses requiring resiliency and business continuity.

Redundancy options in Azure Cache for Redis

Azure Cache for Redis is increasingly becoming critical to our customers’ data infrastructure. As a fully managed service, Azure Cache for Redis provides various high availability options. By default, caches in the standard or premium tier have built-in replication with a two-node configuration—a primary and a replica hosting two identical copies of your data.

New in preview, Azure Cache for Redis can now support up to four nodes in a cache distributed across multiple availability zones. This update can significantly enhance the availability of your Azure Cache for Redis instance, giving you greater peace of mind and hardening your data architecture against unexpected disruption.

#announcements #azure cache #redis #azure cache for redis

What is GEEK

Buddha Community

Zone Redundancy for Azure Cache for Redis now in preview
Ssekidde  Nat

Ssekidde Nat

1624883340

Zone Redundancy for Azure Cache for Redis now in preview

Between waves of pandemics, hurricanes, and wildfires, you don’t need cloud infrastructure adding to your list of worries this year. Fortunately, there has never been a better time to ensure your Azure deployments stay resilient. Availability zones are one of the best ways to mitigate risks from outages and disasters. With that in mind, we are announcing the preview for zone redundancy in Azure Cache for Redis.

Availability Zones on Azure

Azure Availability Zones are geographically isolated datacenter locations within an Azure region, providing redundant power, cooling, and networking. By maintaining a physically separate set of resources with the low latency from remaining in the same region, Azure Availability Zones provide a high availability solution that is crucial for businesses requiring resiliency and business continuity.

Redundancy options in Azure Cache for Redis

Azure Cache for Redis is increasingly becoming critical to our customers’ data infrastructure. As a fully managed service, Azure Cache for Redis provides various high availability options. By default, caches in the standard or premium tier have built-in replication with a two-node configuration—a primary and a replica hosting two identical copies of your data.

New in preview, Azure Cache for Redis can now support up to four nodes in a cache distributed across multiple availability zones. This update can significantly enhance the availability of your Azure Cache for Redis instance, giving you greater peace of mind and hardening your data architecture against unexpected disruption.

#announcements #azure cache #redis #azure cache for redis

Loma  Baumbach

Loma Baumbach

1596679140

Redis Transactions & Long-Running Lua Scripts

Redis offers two mechanisms for handling transactions – MULTI/EXEC based transactions and Lua scripts evaluation. Redis Lua scripting is the recommended approach and is fairly popular in usage.

Our Redis™ customers who have Lua scripts deployed often report this error – “BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE”. In this post, we will explain the Redis transactional property of scripts, what this error is about, and why we must be extra careful about it on Sentinel-managed systems that can failover.

Redis Lua Scripts Diagram - ScaleGrid Blog

Transactional Nature of Redis Lua Scripts

Redis “transactions” aren’t really transactions as understood conventionally – in case of errors, there is no rollback of writes made by the script.

Atomicity” of Redis scripts is guaranteed in the following manner:

  • Once a script begins executing, all other commands/scripts are blocked until the script completes. So, other clients either see the changes made by the script or they don’t. This is because they can only execute either before the script or after the script.
  • However, Redis doesn’t do rollbacks, so on an error within a script, any changes already made by the script will be retained and future commands/scripts will see those partial changes.
  • Since all other clients are blocked while the script executes, it is critical that the script is well-behaved and finishes in time.

The ‘lua-time-limit’ Value

It is highly recommended that the script complete within a time limit. Redis enforces this in a weak manner with the ‘lua-time-limit’ value. This is the maximum allowed time (in ms) that the script is allowed to run. The default value is 5 seconds. This is a really long time for CPU-bound activity (scripts have limited access and can’t run commands that access the disk).

However, the script is not killed when it executes beyond this time. Redis starts accepting client commands again, but responds to them with a BUSY error.

If you must kill the script at this point, there are two options available:

  • SCRIPT KILL command can be used to stop a script that hasn’t yet done any writes.
  • If the script has already performed writes to the server and must still be killed, use the SHUTDOWN NOSAVE to shutdown the server completely.

It is usually better to just wait for the script to complete its operation. The complete information on methods to kill the script execution and related behavior are available in the documentation.

#cloud #database #developer #high availability #howto #redis #scalegrid #lua-time-limit #redis diagram #redis master #redis scripts #redis sentinel #redis servers #redis transactions #sentinel-managed #server failures

Redis Labs Partners with Microsoft to Deliver a New Redis Cache

In a recent blog post, Microsoft announced a new partnership with Redis Labs to deliver Redis Enterprise as newly, fully integrated tiers of Azure Cache for Redis. The enhanced service offering, currently in private preview, will provide customers with two new Enterprise tiers – which include Redis on Flash, modules, and the ability to create an active geo-redundant cache for hybrid-cloud architectures in the future.

Microsoft started their collaboration with Redis Labs back in 2014 with the launch of Redis Cloud on Azure. Since then the service has evolved with updates such as geo-replication support and reserved-capacity. Now, the public cloud vendor incorporates two existing offerings of Redis Labs as additional Enterprise tiers in Azure Redis Cache service providing customers with more features, higher availability, and security capabilities.

Ofer Bengal, CEO and co-founder of Redis Labs, wrote in his blog post on the new partnership announcement:

Throughout the development process, three key customer drivers were consistently top of mind: improve developer productivity, ensure operational resiliency, and ease cloud migration. Teams at both organizations were committed to building an integration that delivers these values to our customers. With the announcement of Redis Enterprise integration into Azure Cache for Redis, we meet these needs.
With the new tiers, developers can use the most up-to-date version of Redis, including its native data structures, probabilistic data structures, streams, time-series, and search data models. Furthermore, they can benefit from the native integration with other Azure services, and easily deploy a Redis cluster and scale to terabyte-sized data sets at the cost of a disk-based data store by utilizing Redis on Flash technology. Also, with the added support of the Redis modules

RediSearch, RedisTimeSeries, and RedisBloom developers can build applications for a wide variety of use cases with a single technology.

#microsoft azure #clustering & caching #redis #microsoft #cloud #distributed cache #caching #devops #architecture & design #development #news

Ruthie  Bugala

Ruthie Bugala

1619623920

Redis Labs Announces General Availability for Integrated Enterprise Tiers of Azure Cache

Recently, Redis Labs announced the general availability of Redis Enterprise-powered tiers on Azure Cache for Redis at the Microsoft Ignite 2021 event. The availability of the Enterprise tiers is said to enable companies to more effectively optimise for low-latency data access in their most critical applications.

The combination of Redis Enterprise and Azure Cache for Redis enables companies to always have access to the latest enterprise-grade Redis functionality, expanded use cases, and enterprise-grade active geo-replication deployment architected for five-nine uptime. It will also offer unique benefits to developers, operators, and ultimately the customer’s bottom line.

According to sources, the Enterprise tiers are fully managed by Microsoft and are the result of a year-long collaboration between the companies to provide the most highly available, resilient, scalable, and extensible Redis service to customers.

#news #azure cache for redis #microsoft azure #redis

Wasswa  Meagan

Wasswa Meagan

1622631660

Microsoft Annonce la Redondance de Zone dans le cache Azure pour Redis

Microsoft a récemment annoncé que le cache Azure pour Redis supportera des zones de disponibilités multiples, augmentant sa disponibilité et résilience. La mise à jour du service permettra aux clients d’améliorer significativement la disponibilité du Cache Azur pour leur instance Redis.

Auparavant, le Cache Azure pour Redis standard ou premium avait une réplication intégrée avec une configuration à deux nœuds – un primaire et un réplica avec deux copies identiques de leurs données. Avec le support des zones de disponibilités, qui sont des centres de données isolés géographiquement au sein d’une région Azure, fournissant une redondance de l’alimentation, le refroidissement, et le réseau, le service dispose maintenant d’une sécurité supplémentaire.

Kyle Teegarden, manager en marketing produit chez Microsoft, a écrit ce qui suit, dans un article de blog à propos du support des zones de disponibilités du Cache Azure pour Redis :

Même avec plus de répliques, une panne dans un centre de données va perturber votre application. C’est pourquoi nous utilisons la redondance de zone, permettant aux répliques d’être localisées dans différentes zones de disponibilités. Les nœuds de réplications peuvent être placés dans une ou plusieurs zones de disponibilités, avec des basculements automatiques entres les zones de disponibilités si nécessaire.

#redis #caching #cloud #azure