-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
CouchDB not starting with default parameters #660
Comments
I also experienced this and @guanana's solution above is the simplest solution. I'm adding my symptoms here for anybody else that might encounter the same... Symptoms
Bad solutionI suspected the CouchDB container wasn't getting enough resources, so I commented out the # deploy:
# resources:
# limits:
# cpus: '0.30'
# memory: 256M
# reservations:
# cpus: '0.15'
# memory: 128M The memory usage climbed to ±1.5GB and the CPU was still 100%, but the I also tried bumping the CouchDB version to I kept searching the webs and found this reported issue with @guanana's solution! 🕺 |
BUG REPORT
Description
swarmpit does not start. It seems to be a problem with couchdb container
Steps to reproduce the issue:
What happens:
The app never starts since couch db is NOT available
What should happen:
CouchDB should start properly so the app can connect and start using the DB
Additional information (e.g. docker version, cluster setup,...):
I solved the problem by adding manually the following on the deployment file:
Section separated for clarity on what was added:
Before that the DB was just hanging and the app unable to connect saying
Connection refused
.Waiting for more than 10% CPU topping up and nothing happened.
Change the ulimits for the couchdb container and I get a healthy connection almost immediately.
The text was updated successfully, but these errors were encountered: