-
Notifications
You must be signed in to change notification settings - Fork 567
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
Multiple DB instance on single Docker block CPU core #235
Comments
Can you give all the commands you ran and any relevant files or logs for reproducing the issue |
I am using redis npm to make connection to redis server and in its configuration is something like this - const RedisClient = Redis.createClient({host: , db: 0}) from microservice 1 and I am not sure if this is the cause of issue, but this was the only change that I brought in already running server. I am observing this issue on two my amazon EC2 server instance after making this change. The docker image for redis in 4.0.9. |
See https://github.com/docker-library/docs/pull/1571/files (duplicate of #217, #225, and probably others) TL;DR, you exposed your Redis server(s) publicly to the internet without a password, and they are now compromised. I'd suggest throwing those containers away completely and creating fresh containers with a password configured and/or without exposing the ports to the internet. |
I am having two microservices using the same redis server running via docker. Both of then are configured to use different db i.e. db0 and db1 in redis. However after some time I am observing both of the CPU core are being used 100% by redis.
The text was updated successfully, but these errors were encountered: