We tried using Motor in our production environment, which has servers running 8 Tornado processes each.
Each process does some DB queries to MongoDB, using Motor.
Each server runs a single mongos instance to which all 8 processes connect locally.

We handle around 2k requests per second, and we noticed that there has been a growing number of open connections to our MongoDB servers, over time.

At the moment, I can't remember whether these connections were local (processes to mongos) or remote (mongos to mongo servers).

For the time being, we've implemented a thread pool solution calling pymongo synchronously, but we'd really like to use Motor, since it's native Tornado.

Is the connection "leak" a known problem? is there a way for us to force close connections? Like I said, I'm not sure if these connections are local or remote, but I guess if Motor leaves an open connection, so will mongos.

Your help is appreciated!

• Roi