Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-4688

Move to Django RedisCache

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • API
    • 5
    • False
    • None
    • False

      Django 4.0 added a RedisCache which we originally moved to when upgrading to Django 4. Previously we were using django-redis.

      Prior to release, QE discovered some issues related to how the application responds when the redis connection is down.

      django-redis had a IGNORE_EXCEPTIONS setting that we used. It's possible that redis was always having connectivity issues in ephemeral and it is now only visible because we are no longer ignoring these exceptions.

      With Django's RedisCache, it does not have any particular settings. Any values in OPTIONS are just passed directly to redis-py.

      With redis-py, there are settings to ignore certain errors as well as define a retry strategy. We need to determine equivalent settings in redis-py that give us the behavior we had with django-redis.

            Unassigned Unassigned
            rh-ee-sdoran Sam Doran
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: