Replies: 5 comments
-
What's the exact error did you get? JuiceFS doesn't force any time out, but if the object storage returns an error, the gc fails as expected. |
Beta Was this translation helpful? Give feedback.
-
MinIO logs that the client ends the connection at the ~30s mark. |
Beta Was this translation helpful? Give feedback.
-
This error means you didn't get response header for 30s after fully writing the request, which usually indicates critical server or network issues. So I suggest checking the MinIO and network configurations first. Line 42 in c8f48b8 |
Beta Was this translation helpful? Give feedback.
-
Thank you much @SandyXSD for taking time to look at this! I appreciate it! FWIW It looks like this has been a long standing issue that MinIO takes a long time to do ListAll, as I see the same question asked and many github tickets for it. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the information! We can leave this issue open to see if anyone else is experiencing similar problems. |
Beta Was this translation helpful? Give feedback.
-
What happened:
juicefs gc fails after 30 seconds when it times out on ListAll
What you expected to happen:
For it to succeed.
How to reproduce it (as minimally and precisely as possible):
execute: juicefs gc 'mysql://user:pass@(fqdn:3306)/bucket'
Anything else we need to know?
juicefs version 1.1.2+2024-02-04.8dbd89a on MinIO VERSION 2024-05-10T01:41:38Z and Percona XtraDB Ver 8.0.36-28.1 for Linux on x86_64 (Percona XtraDB Cluster (GPL), Release rel28, Revision bfb687f, WSREP version 26.1.4.3)
Looking at the MinIO S3 trace the remote connection disconnects at the 30 second mark before it completes the ListAll. I cannot find a way to set the juicefs timeout for this.
Beta Was this translation helpful? Give feedback.
All reactions