You begin maintain golang mongo driver based on go-mgo/mgo? about mgo HOT 5 CLOSED

Hi @xkeyideal

Yes, we (@globalsign) are maintaining this fork of mgo that we use internally - we're committed to keeping it alive and updated for the long term and are open to PRs from others :)

We merge PRs into development, which is then tested in a sharded, replicated environment in our datacenter for regressions. Once everyone is happy, we merge to master - this is to maintain a bit of quality control past the usual PR process.

from mgo.

Please see the issue
https://github.com/go-mgo/mgo/issues/487

from mgo.

I found the reason, see the issue.

I think you should fix it, the mode of nearest should visit localhost server mongodb possibly, not just check the network latency.

from mgo.

Hi @xkeyideal

If you want to talk to the local database only and ignore the rest of the cluster, you should use the connect=direct dial string parameter - check the documentation.

The current behaviour works for our needs and seems to be correct so we won't be changing it ourselves. Saying that, if you think the current behaviour is broken you're welcome to open a PR.

Dom

from mgo.

I know connect=direct, but if the local database disconnect, then the server will down.

So I need nearest support as the mongodb documentation.

from mgo.