-
Notifications
You must be signed in to change notification settings - Fork 155
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
[leo_gateway] Crash when multiple clients requesting the same large object without disk cache #433
Comments
Note that this problem still exists with 1.4.0-pre3 Test Case$ ./s3cmd put testfile s3://test/test
WARNING: Module python-magic is not available. Guessing MIME types based on file extensions.
testfile -> s3://test/test [part 1 of 7, 15MB]
15728640 of 15728640 100% in 0s 62.58 MB/s done
testfile -> s3://test/test [part 2 of 7, 15MB]
15728640 of 15728640 100% in 0s 59.67 MB/s done
testfile -> s3://test/test [part 3 of 7, 15MB]
15728640 of 15728640 100% in 0s 49.73 MB/s done
testfile -> s3://test/test [part 4 of 7, 15MB]
15728640 of 15728640 100% in 0s 60.85 MB/s done
testfile -> s3://test/test [part 5 of 7, 15MB]
15728640 of 15728640 100% in 0s 47.69 MB/s done
testfile -> s3://test/test [part 6 of 7, 15MB]
15728640 of 15728640 100% in 0s 59.48 MB/s done
testfile -> s3://test/test [part 7 of 7, 10MB]
10485760 of 10485760 100% in 0s 51.72 MB/s done With two consoles, $ ./s3cmd get s3://test/test dl1
s3://test/test -> dl1 [1 of 1]
104857600 of 104857600 100% in 0s 135.81 MB/s done $ ./s3cmd get s3://test/test dl2
s3://test/test -> dl2 [1 of 1]
0 of 104857600 0% in 0s 0.00 B/s failed
WARNING: Retrying failed request: /test (EOF from S3!)
WARNING: Waiting 3 sec...
s3://test/test -> dl2 [1 of 1]
104857600 of 104857600 100% in 0s 137.45 MB/s done Log
|
@windkit What did you check the version of Leo's Gateway?
|
The problem also exists when no memory cache is configured
With memory cache, no disk cache
|
@yosukehara Sorry that I added few lines in the source and I forgot to remove them before the test |
I've fixed this issue. It would be nice if you check this, again. |
LGTM. |
Description
Fix for Issue #325 assume disk cache is active.
When disk cache is not configured, 'read' mode client would crash as no cache worker is found.
Moreover, as disk cache is not present, 'read' mode client would not be able to read the object.
Error Log
The text was updated successfully, but these errors were encountered: