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
Api and mc return 0 objects / output when downloading from the same dir at the sametime #4842
Labels
Comments
Concurrent listing showed this problem for me, like if we run the following code concurrently
|
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Aug 22, 2017
Current code was just using io.ReadAll() on an fd() which might have moved underneath due to a concurrent read operation. Subsequent read will result in EOF We should always seek back and read again. pread() is allowed on all platforms use io.SectionReader to read from the beginning of the file. Fixes minio#4842
8 tasks
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Aug 23, 2017
Current code was just using io.ReadAll() on an fd() which might have moved underneath due to a concurrent read operation. Subsequent read will result in EOF We should always seek back and read again. pread() is allowed on all platforms use io.SectionReader to read from the beginning of the file. Fixes minio#4842
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Aug 23, 2017
Current code was just using io.ReadAll() on an fd() which might have moved underneath due to a concurrent read operation. Subsequent read will result in EOF We should always seek back and read again. pread() is allowed on all platforms use io.SectionReader to read from the beginning of the file. Fixes minio#4842
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Aug 23, 2017
Current code was just using io.ReadAll() on an fd() which might have moved underneath due to a concurrent read operation. Subsequent read will result in EOF We should always seek back and read again. pread() is allowed on all platforms use io.SectionReader to read from the beginning of the file. Fixes minio#4842
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Aug 23, 2017
Current code was just using io.ReadAll() on an fd() which might have moved underneath due to a concurrent read operation. Subsequent read will result in EOF We should always seek back and read again. pread() is allowed on all platforms use io.SectionReader to read from the beginning of the file. Fixes minio#4842
deekoder
pushed a commit
that referenced
this issue
Aug 24, 2017
Current code was just using io.ReadAll() on an fd() which might have moved underneath due to a concurrent read operation. Subsequent read will result in EOF We should always seek back and read again. pread() is allowed on all platforms use io.SectionReader to read from the beginning of the file. Fixes #4842
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected Behavior
I would expect the api and mc to beable to do and ls at the same time as a download from a bucket and if they are unable to access not silently fail i.e. the api returning an empty list and mc to none 0.
Current Behavior
While downloading a 100Mb file on one client if a second does a ls in the same bucket and path it will randomly give no results but does not give an error either
Steps to Reproduce (for bugs)
Context
I'm trying to use minio in a CI system which needs to check that all the needed files have been uploaded before it can start testing. The files follow a naming convention but i need to beable to use regex when looking for them so need the ls step before trying to download.
Your Environment
Standalone docker minio container running under docker-ce on centos7
@vadmeste was able to quickly reproduce while I was talking to him in the slack channel
The text was updated successfully, but these errors were encountered: