go-redis/redis · error

redis: NewFailoverClient nil options

Error message

redis: NewFailoverClient nil options

What it means

Error "redis: NewFailoverClient nil options" thrown in go-redis/redis.

Source

Thrown at sentinel.go:536

	if o.TLSConfig != nil && q.has("skip_verify") {
		o.TLSConfig.InsecureSkipVerify = q.bool("skip_verify")
	}

	// any parameters left?
	if r := q.remaining(); len(r) > 0 {
		return nil, fmt.Errorf("redis: unexpected option: %s", strings.Join(r, ", "))
	}

	return o, nil
}

// NewFailoverClient returns a Redis client that uses Redis Sentinel
// for automatic failover. It's safe for concurrent use by multiple
// goroutines.
// Passing nil FailoverOptions will cause a panic.
func NewFailoverClient(failoverOpt *FailoverOptions) *Client {
	if failoverOpt == nil {
		panic("redis: NewFailoverClient nil options")
	}

	if failoverOpt.RouteByLatency {
		panic("to route commands by latency, use NewFailoverClusterClient")
	}
	if failoverOpt.RouteRandomly {
		panic("to route commands randomly, use NewFailoverClusterClient")
	}

	sentinelAddrs := make([]string, len(failoverOpt.SentinelAddrs))
	copy(sentinelAddrs, failoverOpt.SentinelAddrs)

	rand.Shuffle(len(sentinelAddrs), func(i, j int) {
		sentinelAddrs[i], sentinelAddrs[j] = sentinelAddrs[j], sentinelAddrs[i]
	})

	failover := &sentinelFailover{
		opt:           failoverOpt,

View on GitHub (pinned to 36d97525cd)

Solutions

1. Pass a non-nil *FailoverOptions to NewFailoverClient
2. Construct FailoverOptions with at least SentinelAddrs and MasterName

When it happens

Trigger: Thrown at sentinel.go:536 when the library encounters an invalid state.

Common situations: Nil-check options constructors at the application boundary.

AI-assisted analysis of go-redis/redis@36d97525cd (2026-08-06). Data as JSON: /data/errors/c8c94f53fffb38ef.json. Report an issue: GitHub.