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

Metric for file cache size may become negative #4435

Closed
evenyag opened this issue Jul 25, 2024 · 1 comment · Fixed by #4487
Closed

Metric for file cache size may become negative #4435

evenyag opened this issue Jul 25, 2024 · 1 comment · Fixed by #4487
Labels
C-bug Category Bugs

Comments

@evenyag
Copy link
Contributor

evenyag commented Jul 25, 2024

What type of bug is this?

Incorrect result, User Experience

What subsystems are affected?

Standalone mode, Distributed Cluster

Minimal reproduce step

Run the cluster with the experimental write cache enabled

What did you expect to see?

The metric value should be greater than 0.

What did you see instead?

The value of cached bytes is negative:
image

What operating system did you use?

Linux

What version of GreptimeDB did you use?

0.9

Relevant log output and stack trace

No response

@evenyag evenyag added the C-bug Category Bugs label Jul 25, 2024
@evenyag
Copy link
Contributor Author

evenyag commented Jul 25, 2024

Maybe caused by overflow
image

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

Successfully merging a pull request may close this issue.

1 participant