-
Notifications
You must be signed in to change notification settings - Fork 74
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
Again reduce the number of users that GESIS server can have #3083
Comments
Our current assumption is that something goes wrong during the pulling of images when they are not already on the local host. We observed this issue when we tried to launch multiple repositories that required pulling their images from Docker Hub first; 3 out of 5 did not successfully pull.
This might help in reducing the overall load during image pulling. If the issue is indeed related to remote image pulling, I suspect that these reductions could increase the likelihood of successful pulls. However, we should do this only temporarily to debug. Another step we should take is to increase our local image cache or even set up a local image registry configured as a pass-through. This should also help reduce the number of necessary remote pulls from Docker Hub. |
Any ideas beyond that are more than welcome ;) |
Do you have access to the logs or monitoring on your registry server(s)? |
We are using Docker Hub. No logs or monitoring. |
Do you have a paid Docker account, and is anyone else using it?
|
The images are stored under the The But the organisation is own by an paid account. |
Is the BinderHub registry token associated with the paid user account? |
Yes. |
@arnim can you write down here you strategy to search for the reason that GESIS search is unstable as mentioned in #3056?
We talked about (1) drop the GESIS server contribution to the federation to 10 and (2) drop the server total quota to 10.
After that, you want to stress test the system with old images that it need to pull from Docker Hub.
@arnim Thanks for the help!
The text was updated successfully, but these errors were encountered: