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

Region 265098266411008(61723, 0) is in ReadOnly state, expect: Writable #4122

Closed
killme2008 opened this issue Jun 8, 2024 · 4 comments
Closed
Assignees
Labels
C-bug Category Bugs

Comments

@killme2008
Copy link
Contributor

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

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

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

@killme2008
Copy link
Contributor Author

@WenyXu Did we figure out the cause of this issue?

@WenyXu
Copy link
Member

WenyXu commented Jun 19, 2024

@WenyXu Did we figure out the cause of this issue?

Yes, the datanode ran out of CPU resources 🥲, and it can't send any heartbeats to metasrv at that moment.

@killme2008
Copy link
Contributor Author

How and when to fix it? @WenyXu

@WenyXu
Copy link
Member

WenyXu commented Jun 19, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category Bugs
Projects
None yet
Development

No branches or pull requests

2 participants