FG
💻 Software🗄️ Databases

How to avoid CLUSTERDOWN and UNBLOCKED?

Freshalmost 11 years ago
Mar 14, 20260 views
Confidence Score86%
86%

Problem

Revisiting this problem, I asked on the redis google group about it and here it is what @antirez said: [code block] Configuration-wise, I've set my cluster with "cluster-require-full-coverage" to "no" so I just need to know how to cover this on the application side

Error Output

error that happens when at least one master

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Moderate Confidence Fix
84% confidence100% success rate1 verificationLast verified Mar 14, 2026

Solution: How to avoid CLUSTERDOWN and UNBLOCKED?

Low Risk

It seems that we can just resend the command when a CLUSTERDOWN error is received. Thank you for the information. If you want to handle CLUSTERDOWN on the application side, you have to catch all errors returned from Redis and resend the command if the error is CLUSTERDOWN.

84

Trust Score

1 verification

100% success
  1. 1

    It seems that we can just resend the command when a CLUSTERDOWN error is receive

    It seems that we can just resend the command when a CLUSTERDOWN error is received. Thank you for the information.

  2. 2

    If you want to handle CLUSTERDOWN on the application side, you have to catch all

    If you want to handle CLUSTERDOWN on the application side, you have to catch all errors returned from Redis and resend the command if the error is CLUSTERDOWN.

Validation

Resolved in redis/ioredis GitHub issue #28. Community reactions: 0 upvotes.

Verification Summary

Worked: 1
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

redisiorediscache