steve-rodriguez

How do you go about tuning those? How do you know what to set them to? Are there guidelines?

So are BOTH issues fixed? The master/slave issue AND the one where the ConnectionPool gem throws the ConnectionPool::PoolShuttingDownError when you restart a VM where a mongo primary is running? If...

Still seeing this error when a mongo db node is killed. Moped should evict this bad connection. I am assuming since this issue is still open that this was NOT...

To provide more information on this issue, I have a 3 node replica set ( node1, node2 and node3 ). Node1 is the primary. When node2 (secondary node ) is...

Will do. Thx. From: Joel Niedfeldt [mailto:[email protected]] Sent: Friday, February 27, 2015 4:38 PM To: mongoid/moped Cc: Rodriguez, Steve Subject: Re: [moped] Moped is utilizing 'bad' Connections from the connection...

@niedfelj I tried this branch and it appears the ConnectionPool::PoolShuttingDownError has gone away, BUT when stepping down the primary, I see these errors now: Moped::Errors::ConnectionFailure (Could not connect to a...

The 2.0.4 branch does throws those, BUT it actually does reconnect when retrying I believe. I will do some more testing to verify

Ok, heres the scoop to reproduce this issues. You have a 3 node replicaset ( n1-primary, n2-secondary and n3-secondary ) TEST1 - Good Behavior: If you have just restarted your...

@niedfelj @fedenusy @durran . Please advise on my prior comments. Thanks!

@wandenberg Here is our environment: 1) 3 nodes ( 1 primary and 2 secondaries ) on 3 different RHEL vms 2) pool_size for testing purposes is 10. I can make...