-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
minio buckets are missing #1853
Comments
info: https://blog.min.io/configurable-data-and-parity-drives-on-minio-server/ I see that we're setting the environment variable MINIO_STORAGE_CLASS_STANDARD=EC:3 in the Minio Helm values file:
|
my bad: the logic for the new [Controller(IgnoreWhenNotInPod = true)] attribute property was incorrect. |
It looks like minio isn't working anymore because the verson we're on is 1 year old. I've been trying to track down the cluster operator performance issue and found that minio-ss is pegging the CPU and loki-ingestor is also struggling (probably trying to do S3 operations) and loki-compactor and a few other mimir are crashing.
Note that the cluster seemed fine with low CPU utilization at first and for maybe an hour or two while I was working and then went bad overnight.
cluster info: tiny Hyper-V but with 16 GiB RAM,
minio-ss log:
This is a bit confusing though:
ERROR: Unable to initialize storage class config: Standard storage class parity 3 should be less than or equal to 2 (*fmt.wrapError)
This could be bad, but it doesn't look like this was fatal:
https://blog.min.io/configurable-data-and-parity-drives-on-minio-server/
You are running an older version of MinIO released 1 year ago
I think this is just informational. At first, I thought this might be fatal, but that would be crazy.
Status: 4 Online, 0 Offline.
This seems to imply that things are fine.
loki-distributor log
The text was updated successfully, but these errors were encountered: