Replies: 1 comment
-
|
I think this was a symptom of a larger issue. Lots more detail here: https://github.com/orgs/GreptimeTeam/discussions/7580 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I recently move my greptimedb instance to a dedicated vm, and configured the storage to be an S3 compatible destination. Specifically the S3 endpoint that NetApp provides.
I'm still on 0.17.2 while I finish migrating data. It is still inside a docker container.
I'm querying via Grafana and the MySQL endpoint.
Unfortunately, I've been running into errors like this: (redacted bits because I'm paranoid)
That specific example comes from:
When querying my data. So far I haven't figured out a pattern for which queries end up with an error, or which work just fine. And plenty do work just fine.
My searches haven't really uncovered anything. So I'm not sure where the issue might be. Anyone have any ideas?
Edit: Oh, I should mention that is the error Grafana is displaying when I run that query via the Explore interface.
Edit 2: Er. I'm pretty sure this is because my S3 bucket hit the quota limit. Does that seem right?
Beta Was this translation helpful? Give feedback.
All reactions