probably elasticache redis bug when updating to v7.0.7 with dualstack connection

1

Hi All, We just updated our redis cluster in elasticache redis cluster from v7.0.5 to v7.0.7 with dualstack connection and it just went down and keep resetting all incoming connections. After investigation, we found out it may be a bug that can reproduce on all AWS account

expected output: Everything should works fine after redis upgrade

actual output: redis cluster keep reset all incoming connections

step to reproduce:

  1. Open a new redis cluster with the following settings: choose "dualstack" in connection section instead of default ipv4 option choose redis v7
  2. check if AWS choose v7.0.7, we can only reproduce this in v7.0.7, not v7.0.5 not v6.2 or v6
  3. try to connect to this redis cluster and will find out all connection refused.

use nping to test and get all connection refused

Thanks for every folks in AWS User Group Taiwan that help us to narrow down the issue

Original Post on Facebook in Chinese Traditional: https://www.facebook.com/groups/awsugtw/posts/5984294404980354/

asked a year ago516 views
1 Answer
1

Hi, Thanks for reaching out. The fix for it has been deployed in the latest v7.0 update. Your clusters should already be fixed at this point.

AWS
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions