Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Redis Cluster issue during roll outs of new nodes with same addr #1914

Merged
merged 3 commits into from Oct 4, 2021

Commits on Oct 2, 2021

  1. fix: recycle connections in some Redis Cluster scenarios

    This issue was surfaced in a Cloud Provider solution that used for
    rolling out new nodes using the same address (hostname) of the nodes
    that will be replaced in a Redis Cluster, while the former ones once
    depromoted as Slaves would continue in service during some mintues
    for redirecting traffic.
    
    The solution basically identifies when the connection could be stale
    since a MOVED response will be returned using the same address (hostname)
    that is being used by the connection. At that moment we consider the
    connection as no longer usable forcing to recycle the connection.
    pfreixes committed Oct 2, 2021
    Copy the full SHA
    9375185 View commit details
    Browse the repository at this point in the history

Commits on Oct 4, 2021

  1. Copy the full SHA
    129a05d View commit details
    Browse the repository at this point in the history
  2. chore: use switch

    pfreixes committed Oct 4, 2021
    Copy the full SHA
    e0d103c View commit details
    Browse the repository at this point in the history