# Sentinel：仲裁节点超时，主节点 'mymaster' 的故障转移已中止

- **ID:** `redis/sentinel-arbiter-timeout-failover`
- **领域:** redis
- **类别:** network_error
- **错误码:** `SENTINEL`
- **验证级别:** ai_generated
- **修复率:** 78%

## 根因

故障转移投票期间，Sentinel 仲裁节点未在配置的超时时间内响应，导致无法达到法定人数。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| 6.2 | active | — | — |
| 7.0 | active | — | — |
| 7.2 | active | — | — |

## 解决方案

1. ```
   Increase the sentinel failover-timeout to give the arbiter more time to respond. Example: SENTINEL SET mymaster failover-timeout 60000 (from 30000 ms default)
   ```
2. ```
   Check network connectivity between the Sentinel nodes and the arbiter; reduce latency by ensuring they are in the same datacenter or use a faster network path.
   ```
3. ```
   If the arbiter is unreliable, replace it with a more stable Sentinel instance or remove it from the sentinel monitor configuration.
   ```

## 无效尝试

- **Increase the sentinel monitor quorum to a higher value to require more votes.** — This increases the required votes but does not fix the arbiter timeout; it may make failover even harder. (60% 失败率)
- **Set all Sentinels to have equal weight by removing arbiter designation.** — Arbiters are a concept in some setups; in Redis Sentinel, all nodes vote equally, and removing designation does not address timeout. (70% 失败率)
- **Restart the arbiter Sentinel node to clear its state.** — If the timeout is due to network or resource issues, restarting provides only temporary relief. (50% 失败率)