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
why scanning? #36
Comments
The scanning process is to handle replica sets ( Mongolian DB will connect to the specified mongo server(s), ask them if In a single-server setup, this process is pretty simple and fast since there |
shouldn't the messages only be printed when debugging, then? |
It's the default console logging. There's no standard node.js "debugging" mode that is appropriate here, so if you want to change the logging style, pass a custom logger into the constructor as described in the readme. |
"debugging" in the sense of "I need that kind of information and for that reason set a custom logger". |
Although mongolian gets passed in the connection information
it prints
which suggests it's searching for mongo. Why the scanning?
The text was updated successfully, but these errors were encountered: