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

(error) ERR Writing binlog failed, maybe no space left on device 空间写满后无法恢复 #2520

Open
maoliugang opened this issue Mar 15, 2024 · 5 comments
Labels
☢️ Bug Something isn't working good first issue

Comments

@maoliugang
Copy link

Is this a regression?

No

Description

pika在磁盘写爆之后出现报错(error) ERR Writing binlog failed, maybe no space left on device
此时清理磁盘空间之后,依然无法写入数据
image

Please provide a link to a minimal reproduction of the bug

No response

Screenshots or videos

images
5e19049ba9e9a154c13b6ede849da28

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

版本 3.5.0

Anything else?

No response

@maoliugang maoliugang added the ☢️ Bug Something isn't working label Mar 15, 2024
@maoliugang maoliugang changed the title (error) ERR Writing binlog failed, maybe no space left on device 无法 (error) ERR Writing binlog failed, maybe no space left on device 空间写满后无法恢复 Mar 15, 2024
@Mixficsol
Copy link
Collaborator

Mixficsol commented Mar 15, 2024

#1843 尝试一下用 diskrecovery 命令呢

@chejinge
Copy link
Collaborator

您好 这个问题可以先用diskrecovery恢复数据写,等到恢复后看看能不能把与数据无关的日志或者什么删除一下,或者尝试做配置低峰期及时做compact及时清除碎片化数据的操作,这个删除数据这个事情,我们需要讨论在开发下看怎么做

@Issues-translate-bot
Copy link

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


Hello, for this problem, you can use diskrecovery to restore the data writing first. After the recovery, see if you can delete the logs or other things that have nothing to do with the data, or try to configure the operation of compacting and clearing the fragmented data in time during the off-peak period. This deletion Regarding data, we need to discuss how to do it under development

@AlexStocks
Copy link
Collaborator

AlexStocks commented Mar 27, 2024

发生这种问题的时候,通过如下方式解决:
step1:提前监控 pika 日志,当磁盘快满的时候,pika 就会打印日志,可以提前删除磁盘上上无用的数据【如日志】,以解决问题;
step2:如果磁盘已经满溢,此时 Pika 会进入自我保护状态,请先删除磁盘上其他应用的数据,清空磁盘后,向 Pika 发送
diskrecovery 命令,此时磁盘会恢复数据写;
step3:平时尝试做配置低峰期及时做 compact 及时清除碎片化数据的操作。

@Issues-translate-bot
Copy link

Issues-translate-bot commented Mar 27, 2024

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


When this problem occurs, solve it in the following ways:
Step 1: Monitor the pika log in advance. When the disk is almost full, pika will print the log. You can delete useless data [such as logs] on the disk in advance to solve the problem;
step2: If the disk is full, Pika will enter the self-protection state. Please delete the data of other applications on the disk first, clear the disk, and send diskrecovery command to Pika, at this time the disk will resume data writing;
Step 3: Usually try to compact and clear fragmented data in a timely manner during low peak periods of configuration.

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

No branches or pull requests

5 participants