-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Connection pool not working correctly #140
Comments
Hi, thanks for opening this issue. If you could, provide the following to
make it a little easier to work this out:
1. You said you have a connection error. Can you please paste the error +
stack trace, along with reproduction steps?
2. What specifically do you mean by “This is also not working”?
…On Sat, Dec 29, 2018 at 9:37 AM sstinger ***@***.***> wrote:
If I use new Db.pool with WriteConcern.JOURNALED and one Server of the
Cluster is down I get a connection error.
Is this correct or is there an other possibility to connect to a cluster?
new Db("mongodb://127.0.0.1:27017,127.0.0.1:27018,127.0.0.1:27019/test");
This is also not working.
Can't I auto failover to the primary with this lib?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#140>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJiKPIwPTStDWPDqaVXYZ9brIHH9RRiEks5u934tgaJpZM4ZkmNN>
.
|
Thx for the quick reply.
So I thought I can use the pool function to do that:
If all three nodes are Online and healthie it's working but if one node goes down (no matter which one) I get this Exception:
How can I alternatively failover in a replica set? I hope you understand my question and excuse my bad english |
@thosakwe did you ever find a solution to this? This is a blocker for me right now |
I would be glad if you use this package that I have just developed. I continue to develop and have plans to bring a lot of features. |
If I use new Db.pool with WriteConcern.JOURNALED and one Server of the Cluster is down I get a connection error.
Is this correct or is there an other possibility to connect to a cluster?
new Db("mongodb://127.0.0.1:27017,127.0.0.1:27018,127.0.0.1:27019/test");
This is also not working.
Can't I auto failover to the primary with this lib?
The text was updated successfully, but these errors were encountered: