DocumentationCommerceCommerce KB

Managed alerts on Adobe Commerce: Redis memory critical alert

Last update: Thu Jul 27 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin

This article provides troubleshooting steps for when you receive a Redis memory critical alert for Adobe Commerce in New Relic. Immediate action is required to resolve the issue. The alert will look something like the following, depending on the alert notification channel you selected.

new_relic_redis_memory_critical.png

Affected products and versions

All versions of Adobe Commerce on cloud infrastructure Pro plan architecture

Issue

You will receive an alert in New Relic if you have signed up to Managed alerts for Adobe Commerce and one or more of the alert thresholds have been surpassed. These alerts were developed by Adobe to give merchants a standard set of alerts using insights from Support and Engineering.

Do!

  • Abort any deployment scheduled until this alert is cleared.
  • Put your site into maintenance mode immediately if your site is or becomes completely unresponsive. For steps refer to Installation Guide > Enable or disable maintenance mode in our Installation Guide. Make sure to add your IP to the exempt IP address list to ensure that you are still able to access your site for troubleshooting. For steps, refer to Maintain the list of exempt IP addresses in our Installation Guide.

Don’t!

  • Launch additional marketing campaigns which may bring additional pageviews to your site.
  • Run indexers or additional crons which may cause additional stress on CPU or disk.
  • Do any major administrative tasks (i.e., major action in the Commerce Admin such as data imports / exports, flushing media, saving categories with a great number of assigned products, and mass updates).
  • Clear your cache.

Solution

Follow these steps to identify and troubleshoot the cause.

Because this is a critical alert, it is highly recommended you complete Step 1 before you try to troubleshoot the issue (Step 2 onwards).

  1. Check if an Adobe Commerce support ticket exists. For steps, refer to Track your support tickets in our support knowledge base. Support may have already received a New Relic threshold alert, created a ticket and started working on the issue. If no ticket exists, create one. The ticket should have the following information:

  2. If no support ticket exists, check if Redis Used Memory is increasing or decreasing by going to one.newrelic.com > Infrastructure > Third-party services page, select the Redis dashboard. If it is stable or increasing, submit a support ticket to have your cluster upsized, or increase the maxmemory limit to the next level.

  3. If you cannot identify the cause of increased Redis memory consumption, review recent trends to identify issues with recent code deployments or configuration changes (for example, new customer groups and large changes to the catalog). It is recommended that you review the past seven days of activity for any correlations in code deployments or changes.

  4. Check for misbehaving third party extensions:

    • Try to find a correlation with recently installed third party extensions and the time the issue started.
    • Review extensions which potentially could affect the Adobe Commerce cache and cause the cache to grow quickly. For example, custom layout blocks, overriding cache functionality, and storing large amounts of data in cache.

  5. If there is no evidence of misbehaving extensions, Install latest patches to fix Redis issues for Adobe Commerce on cloud infrastructure.

  6. If the above steps do not help you identify or troubleshoot the source of the issue, consider enabling L2 cache to reduce network traffic between the app and Redis. For general information on what is L2 cache, refer to L2 caching in the Adobe Commerce application in our developer documentation. To enable L2 cache for cloud infrastructure, try the following:

    • Upgrade ECE Tools if below 2002.1.2 version.
    • Configure L2 Cache by using Use REDIS_BACKEND variable and updating .magento.env.yaml file:
    code language-yaml 
    stage:
    deploy:
        REDIS_BACKEND: '\Magento\Framework\Cache\Backend\RemoteSynchronizedCache'
recommendation-more-help
8bd06ef0-b3d5-4137-b74e-d7b00485808a