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

[Bug] The values of FENCED_BIT and LOGIC_DISK_FULL_BIT in RunningFlags conflict #7574

Closed
3 tasks done
RongtongJin opened this issue Nov 20, 2023 · 1 comment · Fixed by #7575
Closed
3 tasks done

Comments

@RongtongJin
Copy link
Contributor

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

Linux

RocketMQ version

develop

JDK Version

1.8

Describe the Bug

image

The values of FENCED_BIT and LOGIC_DISK_FULL_BIT in RunningFlags conflict.

Steps to Reproduce

This will cause the broker to be unable to write messages in controller mode

What Did You Expect to See?

The broker can write messages normally

What Did You See Instead?

The broker can not write messages

Additional Context

No response

@RongtongJin
Copy link
Contributor Author

@guyinyou

@RongtongJin RongtongJin changed the title [Bug] The values of FENCED_BIT and LOGIC_DISK_FULL_BIT in RunningFlags conflict. [Bug] The values of FENCED_BIT and LOGIC_DISK_FULL_BIT in RunningFlags conflict Nov 20, 2023
RongtongJin pushed a commit that referenced this issue Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant