-
Notifications
You must be signed in to change notification settings - Fork 188
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
Finding user home space is flaky #3749
Comments
|
The problem happens here https://github.com/cs3org/reva/blob/edge/pkg/storage/utils/filelocks/filelocks.go#L144 We need to find a solution to suppress the error. |
Do we need to always supress the error, or only if we tried to delete a file that does no longer exist? |
From what I witness and the way I understand it the problem occurs when trying to fetch the personal space or upload files into it (also initially when no files are present, but not limited to that) |
Hm, I can trigger
by sending 50-100 concurrent PROPFINDS to a spaces endpoint.
Which is the locking issue mentioned in #3749 (comment) But in your case I was stumbling over |
yes I get this error with the latest master and latest build for osx. For me it fails every time sadly :/ |
First load of the page after login
this happens after i reload a couple of times |
Reason is the flock issue. Closing this in favor of #3757 |
@lookacat your logs indicate a problem with That is a different root cause. could you open a new issue, as #222 is closed. To check the current number of open file descriptors you can use the command in #268 (comment) The solution might be as easy as raising the limit of open file descriptors. The microservice architecture opens quite a lot of tcp connections between different ports. @mmattel I cannot find something on file descriptors / ulimits |
Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Solid loading of personal space
Actual behavior
Flakiness, both when navigating and when doing full-page reloads
Logs
Success case
Failure case
Setup
oCIS on curren master (today 13:00)
The text was updated successfully, but these errors were encountered: