pollutri
/
res_levis_backend
1
0
派生 0
代码 工单 1 合并请求 0 版本发布 0 百科 动态
您最多选择25个主题 主题必须以字母或数字开头，可以包含连字符 (-)，并且长度不得超过35个字符
330 提交
3 分支
9.3 MiB
 
 
 
 
目录树: 4bf1bee89f
分支列表 标签列表
${ item.name }
创建分支 ${ searchTerm }
从 '4bf1bee89f'
${ noResults }
res_levis_backend/vendor/github.com/redis/go-redis/v9/maintnotifications
Blaz Smehov 4bf1bee89f feat: add MQTT -> kafka bridge, template for decoder 1 个月前
..
FEATURES.md feat: add MQTT -> kafka bridge, template for decoder 1 个月前
README.md feat: add MQTT -> kafka bridge, template for decoder 1 个月前
circuit_breaker.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
config.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
errors.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
example_hooks.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
handoff_worker.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
hooks.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
manager.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
pool_hook.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
push_notification_handler.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前
state.go feat: add MQTT -> kafka bridge, template for decoder 1 个月前

README.md

Maintenance Notifications

Seamless Redis connection handoffs during cluster maintenance operations without dropping connections.

⚠️ Important Note

Maintenance notifications are currently supported only in standalone Redis clients. Cluster clients (ClusterClient, FailoverClient, etc.) do not yet support this functionality.

Quick Start

client := redis.NewClient(&redis.Options{
    Addr:     "localhost:6379",
    Protocol: 3, // RESP3 required
	MaintNotificationsConfig: &maintnotifications.Config{
        Mode: maintnotifications.ModeEnabled,
    },
})

Modes

  • ModeDisabled - Maintenance notifications disabled
  • ModeEnabled - Forcefully enabled (fails if server doesn’t support)
  • ModeAuto - Auto-detect server support (default)

Configuration

&maintnotifications.Config{
    Mode:                       maintnotifications.ModeAuto,
    EndpointType:               maintnotifications.EndpointTypeAuto,
    RelaxedTimeout:             10 * time.Second,
    HandoffTimeout:             15 * time.Second,
    MaxHandoffRetries:          3,
    MaxWorkers:                 0,    // Auto-calculated
    HandoffQueueSize:           0,    // Auto-calculated
    PostHandoffRelaxedDuration: 0,    // 2 * RelaxedTimeout
}

Endpoint Types

  • EndpointTypeAuto - Auto-detect based on connection (default)
  • EndpointTypeInternalIP - Internal IP address
  • EndpointTypeInternalFQDN - Internal FQDN
  • EndpointTypeExternalIP - External IP address
  • EndpointTypeExternalFQDN - External FQDN
  • EndpointTypeNone - No endpoint (reconnect with current config)

Auto-Scaling

Workers: min(PoolSize/2, max(10, PoolSize/3)) when auto-calculated Queue: max(20×Workers, PoolSize) capped by MaxActiveConns+1 or 5×PoolSize

Examples:

  • Pool 100: 33 workers, 660 queue (capped at 500)
  • Pool 100 + MaxActiveConns 150: 33 workers, 151 queue

How It Works

  1. Redis sends push notifications about cluster maintenance operations
  2. Client creates new connections to updated endpoints
  3. Active operations transfer to new connections
  4. Old connections close gracefully

For more information, see FEATURES