Closed orxvan closed 2 years ago
- deploy a minio cluster on k8s, version is RELEASE.2020-02-20T22-51-23Z,storage use local volume on every ECS,4nodes.every nodes has 500GB files. *
this looks like we can't write to your drives
- deploy a minio cluster on k8s, version is RELEASE.2020-02-20T22-51-23Z,storage use local volume on every ECS,4nodes.every nodes has 500GB files.
this looks like we can't write to your drives
Thx, but how to reslove or debug it. I try to rm the path where mounted by the local volume,and restart the minio-2,but it not worked
- deploy a minio cluster on k8s, version is RELEASE.2020-02-20T22-51-23Z,storage use local volume on every ECS,4nodes.every nodes has 500GB files.
this looks like we can't write to your drives
Maybe I troubled you,
deploy a minio cluster on k8s, version is RELEASE.2020-02-20T22-51-23Z,storage use local volume on every ECS,4nodes.every nodes has 500GB files.
the old minio cluster works fine for 2 years. It only find in the dest cluster when transfer the date
I transfer the data.(use scp or cp) copy the data from old to the new
Whatever it is you are doing here is not going to work. You should never touch backend files.
We do not provide community support for older MinIO versions. Start with a clean cluster on the newest release.
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
may NOT reproduce.
Context
kubectl delete po minio-2
,can't work redeploy the service , may work, but It's a online service, redpeloy makes the service down.Regression
I google /search the key words ,it always says it's a network error.But I can curl minio-2.minio:9000,just reponse 503 means the node is not fine。
Your Environment
uname -a
):Linux worker-2 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux