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

Please make serverSelectionTimeoutMS configurable as well #72

Closed
bjjl opened this Issue Mar 28, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@bjjl

bjjl commented Mar 28, 2016

Subject says it all. Thanks much! :)

@jakubczaplicki

This comment has been minimized.

Show comment
Hide comment
@jakubczaplicki

jakubczaplicki Sep 30, 2016

+1

Even after setting

    MONGO_CONNECT_TIMEOUT_MS = 1000
    MONGO_SOCKET_TIMEOUT_MS = 1000

PyMongo will still wait default 30 sec until pymongo.errors.ServerSelectionTimeoutError occurs.

Tested in Flask-PyMongo==0.4.1.

jakubczaplicki commented Sep 30, 2016

+1

Even after setting

    MONGO_CONNECT_TIMEOUT_MS = 1000
    MONGO_SOCKET_TIMEOUT_MS = 1000

PyMongo will still wait default 30 sec until pymongo.errors.ServerSelectionTimeoutError occurs.

Tested in Flask-PyMongo==0.4.1.

@matt-snider

This comment has been minimized.

Show comment
Hide comment
@matt-snider

matt-snider Oct 23, 2016

👍

Had the same issue. Hanging the server/worker for 30 seconds on loss of connectivity makes this unusable in production.

matt-snider commented Oct 23, 2016

👍

Had the same issue. Hanging the server/worker for 30 seconds on loss of connectivity makes this unusable in production.

@dcrosta

This comment has been minimized.

Show comment
Hide comment
@dcrosta

dcrosta May 22, 2017

Owner

Added in #80, will be part of a forthcoming 0.5.0 release.

Owner

dcrosta commented May 22, 2017

Added in #80, will be part of a forthcoming 0.5.0 release.

@dcrosta dcrosta closed this May 22, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment