[
https://issues.apache.org/jira/browse/TUBEMQ-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117284#comment-17117284
]
Guocheng Zhang commented on TUBEMQ-157:
---------------------------------------
!screenshot-1.png!
The state change when Broker reports an exception flows according to the above
rules. If the read error still allows data to be written, it is likely that the
disk has failed and cannot be recovered, and the written data cannot be read
out, resulting in data loss.
> Optimize Broker disk anomaly check
> ----------------------------------
>
> Key: TUBEMQ-157
> URL: https://issues.apache.org/jira/browse/TUBEMQ-157
> Project: Apache TubeMQ
> Issue Type: Bug
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Normal
> Attachments: screenshot-1.png
>
>
> When the disk is abnormally read, if the write is still allowed, the written
> data will not be read out, resulting in more data loss. The current
> inspection needs to be adjusted, as long as the read is abnormal, the broker
> should not be able to read and write.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
