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

全量同步过程中,db_repl_state 的状态显示为 WaitDBSync,但是 master_link_status 状态为 down #2428

Closed
chengyu-l opened this issue Feb 28, 2024 · 5 comments
Labels
☢️ Bug Something isn't working

Comments

@chengyu-l
Copy link
Collaborator

Is this a regression?

Yes

Description

将全量同步速度控制在每秒 4KB,降低全量同步速度,一段时间后,master_link_status 状态为 down,但是 db_repl_state 的状态显示为 WaitDBSync。

slave 节点
image

master 节点
image

Please provide a link to a minimal reproduction of the bug

No response

Screenshots or videos

images

Please provide the version you discovered this bug in (check about page for version information)

No response

Anything else?

No response

@chengyu-l chengyu-l added the ☢️ Bug Something isn't working label Feb 28, 2024
@chengyu-l
Copy link
Collaborator Author

chengyu-l commented Feb 28, 2024

master_link_status 字面的含义是 master 连接的状态。有几种修改方法:(1)如果希望表示从节点已完成全量同步,应该更改 master_link_status 的名字(2)如果仅表示 slave 与 master 连接的状态,master_link_status 值,在全量同步时,也应该是 up

@AlexStocks
Copy link
Collaborator

lcy: Redis 也有这个字段,需要根据 Redis 继续推进

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


lcy: Redis also has this field, and it needs to be further developed based on Redis.

@AlexStocks
Copy link
Collaborator

#2689 已经新增 info 指标 "repl_connect_status" 以解决这个问题。

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


#2689 The info indicator "repl_connect_status" has been added to solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
☢️ Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants