We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Unexpected error
Distributed Cluster
In some cases, the region may go into read-only state and can't be recovered at all
Internal Server Error: {\"error\":\"Region 265098266411008(61723, 0) is in ReadOnly state, expect: Writable\"}"
Please investigate and address this issue seriously, as it is impacting availability. @WenyXu @fengjiachun
The region should recover normally even when node crash etc.
The region keeps in a read-only state.
Not relevant
0.8.2
No response
The text was updated successfully, but these errors were encountered:
@WenyXu Did we figure out the cause of this issue?
Sorry, something went wrong.
Yes, the datanode ran out of CPU resources 🥲, and it can't send any heartbeats to metasrv at that moment.
How and when to fix it? @WenyXu
For now, #4128 may mitigate the impact of this problem. However, a better solution is to rely on the region HA mechanism.
WenyXu
No branches or pull requests
What type of bug is this?
Unexpected error
What subsystems are affected?
Distributed Cluster
Minimal reproduce step
In some cases, the region may go into read-only state and can't be recovered at all
Please investigate and address this issue seriously, as it is impacting availability. @WenyXu @fengjiachun
What did you expect to see?
The region should recover normally even when node crash etc.
What did you see instead?
The region keeps in a read-only state.
What operating system did you use?
Not relevant
What version of GreptimeDB did you use?
0.8.2
Relevant log output and stack trace
No response
The text was updated successfully, but these errors were encountered: