Skip to content
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

No retries are made after "failed to connect on first connect" #5280

Closed
barakbd opened this issue Jan 6, 2019 · 2 comments
Closed

No retries are made after "failed to connect on first connect" #5280

barakbd opened this issue Jan 6, 2019 · 2 comments

Comments

@barakbd
Copy link

barakbd commented Jan 6, 2019

Please see issue here: Automattic/mongoose#5169

Same issue occurs in parse-server.

Suggestions?

@barakbd barakbd changed the title No retries are made after "failed to connect on first connect" #5169 No retries are made after "failed to connect on first connect" Jan 6, 2019
@flovilmart
Copy link
Contributor

From what I can read, this behavior is expected from the driver perspective.

Also, parse server has some initialization to perform before it can startup. So it will always expect the DB to be up before it starts.

Even in the docker compose docs, they recommend to add a ‘wait-for-it’ script
https://docs.docker.com/compose/startup-order/ for such behavior. I am not sure we should fix in parse-server

@stale
Copy link

stale bot commented Feb 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants